Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ferrum::ProcessTimeoutError since cuprite bump from 0.13 to 0.14.3 #319

Open
filipefurtad0 opened this issue Dec 8, 2022 · 4 comments
Open

Comments

@filipefurtad0
Copy link

filipefurtad0 commented Dec 8, 2022

Hello 馃憢

We're getting inconsistent failures on our build, since we've bumped Cuprite from 0.13 to 0.14.3.

The error occurs when attempting to visit a URL, on headless chrome (/account in the example below):

     Failure/Error: visit "/account"
     
     Ferrum::ProcessTimeoutError:
       Browser did not produce websocket url within 20 seconds, try to increase `:process_timeout`. See https://github.com/rubycdp/ferrum#customization

This seems like a concurrency issue as increasing a number of parallel tests also increases the chances that this error occurs - we use Knapsack Pro to run parallel tests on Github Actions.

However, the issue was already present, when running the build without the parallel spec strategy. Re-running the spec always makes it pass.

Any ideas/suggestions how fix this issue?

Thanks in advance,
Filipe

@andrewhavens
Copy link

We're also running into this problem. We're also using GitHub Actions for our CI. Randomly, some tests fail with this error. I'm not sure if it's more common when running specs in parallel. I've tried increasing the process timeout to 30 seconds the problem still occurs, so the process timeout config isn't the problem in this particular case. If there was a way to retry a certain number of times, that would probably solve this issue, but I'm not sure how best to do that.

@route
Copy link
Member

route commented Jul 14, 2023

@filipefurtad0 do you still have issues or that was RAM error?
@andrewhavens did you consider it to be RAM error as well?

@andrewhavens
Copy link

@route Seems like it could be a possibility, but how would you go about confirming that it's a RAM error, and how would you fix it? According to the GitHub docs, the ubuntu-latest runner provides 7 GB of RAM (which seems like it would be enough?). The output of the test run looks like this:

2 processes for 123 specs, ~ 61 specs per process

Randomized with seed 49860

Randomized with seed 34500
...........................................F............................F.....................................F......................

Finished in 3 minutes 26.5 seconds (files took 11.24 seconds to load)
128 examples, 0 failures

Randomized with seed 34500

FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF*FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

@route
Copy link
Member

route commented Jul 25, 2023

@andrewhavens if you could turn on debug output of ferrum we could see where it stopped and why.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants