-
-
Notifications
You must be signed in to change notification settings - Fork 1k
Delay loading system test integration #1903
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Delay loading system tests as late as possible in order to allow people who arent using them to not have to turn off puma or other such things. It also enables other webservers to be configured other than puma which is needed in Rails as of rails/rails@50f6976
This seems reasonable, but I don't think I have sufficient context to be the only one to review this. |
This looks right to me. 👍 The main thing is making sure Thanks for making this happen, @JonRowe! |
👍 |
Going to merge this as the build failure is unrelated, will attempt to resolve that when I can |
🎉 |
Delay loading system tests as late as possible in order to allow people who arent using them to not have to turn off puma or other such things. It also enables other webservers to be configured other than puma which is needed in Rails as of rails/rails@50f6976
This got released as 3.7.2, hopefully helps! |
Delay loading system tests as late as possible in order to allow people who arent using them to not have to turn off puma or other such things. It also enables other webservers to be configured other than puma which is needed in Rails as of rails/rails@50f6976
Delay loading system tests as late as possible in order to allow people who arent using them to not have to turn off puma or other such things. It also enables other webservers to be configured other
than puma which is needed in Rails as of rails/rails@50f6976
This should help people who have issues with puma loading when they're not using system test integration. /cc @myronmarston @samphippen @sj26