Specs failing after switching from stimpack to packs-rails with 'packs/rails/rspec' required - unexpected behavior?

This message was imported from the Ruby/Rails Modularity Slack server. Find more info in the import thread.

Message originally sent by slack user U716MSFSMKK

Hi friends! We just went from stimpack > packs-rails and oddly when I require packs/rails/rspec in our .rspec file, we have a few specs that fail. I’m able to get them to pass by not requiring this, but am curious if that’s unexpected behavior. I thought that the only way to run specs for a single package was by requiring that, but I’m still able to run them just fine.

In what way do they fail Sally? cc <@U78561YO9UP>

Message originally sent by slack user U716MSFSMKK

Oops, sorry I meant to add more context to this and spaced. We use rspec-retry to tag our flaky specs so that they retry a certain amount of times in our CI build. The error we get is undefined local variable or method controller’`

Message originally sent by slack user U716MSFSMKK

We don’t see this error when we use stimpack

Message originally sent by slack user U716MSFSMKK

And the error is only happening with our flaky feature specs that are tagged with retry

Interesting, so you’re seeing this only between stimpack and packs-rails and changing string passed into require?

Hmm, any chance you’re able to put together a minimal repro? I know that can be tricky sometimes. I’d also be open to a zoom pairing session if you can’t identify a culprit on your side.