-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Define url_options as per system test case does #2329
base: main
Are you sure you want to change the base?
Conversation
I don't have anymore timeout with the PR, but I had no timeout with I think the problem is related to this: If you do : --- a/Gemfile
+++ b/Gemfile
@@ -5,6 +5,9 @@ ruby '2.6.6'
# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', '6.0.0.rc1'
+gem 'actionpack', '6.0.0.rc1'
+gem 'activesupport', '6.0.0.rc1'
+gem 'railties', '6.0.0.rc1' You do no have the timeout anymore. 🤔 |
@benoittgt Rails 6.0.0.rc1 doesn't have the timeout issue because the problem was first introduced in Rails 6.0.1.rc1. Everything before that, including 6.0.0.rc1 is OK for me as well. |
Sorry... 🤦 |
443fa2b
to
429160d
Compare
@@ -106,4 +106,4 @@ Feature: System spec | |||
When I run `rspec spec/system/widget_system_spec.rb` | |||
Then the output should contain "1 example, 0 failures" | |||
And the output should not contain "starting Puma" | |||
And the exit status should be 0 | |||
And the exit status should be 0 or I debug |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you understand why, I am interested. I wrote this #2325 (comment)
429160d
to
7d0a9af
Compare
49b14cb
to
0623e8a
Compare
0623e8a
to
1b0cc7b
Compare
1b0cc7b
to
08182d3
Compare
Rails switched to manually defining
url_options
when they switched away from inheriting from integration test case.See:
rails/rails@ea77dbf#diff-ff5f366a442b8761d35f94807700fa77R162
This should fix #2327