CI: bump Ferrum/Chrome timeouts #645
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This error is common in CI:
1) Error:
BroadcastsTest#test_Message_broadcasts_with_renderable:_render_option:
Ferrum::ProcessTimeoutError: Browser did not produce websocket url
within 10 seconds, try to increase `:process_timeout`. See
https://github.com/rubycdp/ferrum#customization
Example: https://github.com/hotwired/turbo-rails/actions/runs/9919129989/job/27404623838#step:4:230
It is possible to control this timeout (and another one) via ENV vars:
https://github.com/rubycdp/ferrum/blob/v0.15/lib/ferrum/browser/options.rb#L10-L11
"timeout" is
> The number of seconds we'll wait for a response when communicating with browser. Default is 5.
"process_timeout" is (defaults to 10)
> How long to wait for the Chrome process to respond on startup.
Both ferrum CI and cuprite CI has the timeouts set to 25 and 15:
* https://github.com/rubycdp/ferrum/blob/19767d0885afbebc95574eda685e04dc9da2b47d/.github/workflows/tests.yml#L16-L18
* https://github.com/rubycdp/cuprite/blob/373b894d723bf9fb1afe31781963fe655a177218/.github/workflows/tests.yml#L16-L18
|
Thanks @dentarg! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This error is common in CI:
Example: https://github.com/hotwired/turbo-rails/actions/runs/9919129989/job/27404623838#step:4:230
It is possible to control this timeout (and another one) via ENV vars: https://github.com/rubycdp/ferrum/blob/v0.15/lib/ferrum/browser/options.rb#L10-L11
"timeout" is
"process_timeout" is (defaults to 10)
Both ferrum CI and cuprite CI has the timeouts set to 25 and 15: