Attempt to fix Ferrum timeout errors #1877
Merged
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.
What are you trying to accomplish?
We're seeing quite a few
Ferrum::ProcessTimeoutError: Browser did not produce websocket url within 10 seconds
errors in CI jobs. I did a little digging and discovered the Cuprite driver we're registering in test_helper.rb is getting overwritten by Rails, so it's not using any of the config options we're passing in.What approach did you choose and why?
primer/view_components solved this a while ago by registering a driver with a unique name, so that's what I did here.