-
Notifications
You must be signed in to change notification settings - Fork 3.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
Missing browserCriClient in connectToNewSpec #27657
Comments
here's a couple of snippets from the debug output with can't share the entire thing here, since it's huge and contains sensitive info. if there are select modules we should capture, could try that. note that "sem-pages" is the 2nd spec in this project
it's clear that cypress is killing the browser: |
updates:
hopefully that can maybe help narrow in what might be going on. some outstanding questions:
|
Experiencing this issue as well. Setup:
In another project this issue does not exists. Same pipeline setup but:
Would any of the following help?
|
Quick update from my side:
Do not see any issue anymore... |
I have the same problem.
There is no stable 100% STR, the problem is only on CI, in about 10-20% of cases. After RAM was increased, the problem began to appear a little less often, but it did not disappear completely. I hope you solve this problem or tell a workaround, this problem makes our ci tests unstable |
Any update? |
@Dospios I did some experimenting and it seems like that setting
did help a lot. I also set |
@stfnzl |
@Dospios just for curiosity, do you run cypress and the web server in the same host? |
@stfnzl external url. For each PR, a test stand is deployed, on which autotests are run and manual testing is carried out |
@Dospios thanks for the info. I asked 'cause we run against localhost and wanted to check if separating cypress/chrome and the webserver would have helped, but it is not the case seems like so not gonna spend time on setting it up. I did a "stress test" on our setup by running 20 builds in azure devops which trigger 3 parallelized jobs each (~60 cypress runs) 3.3% failure rate is still too high imo... my goal is to have at least 100 consecutive stable runs (<1% failure rate) ...and the fact that cypress cloud will not report it as failure but rather as a timeout does not help either 😞 |
any update on this? I keep getting this issue consistently while executing the last test on the CI/CD pipeline and nothing seems to fix this. It makes the test unusable! Timed out waiting for the browser to connect. Retrying... Cypress v13.3.0 |
We have different projects running Cypress without any issues, but the only one that is failing with Do you experience the same @abinaya-konda @Dospios? I'm thinking to split the tests in 3 or 4 groups and see if it helps or not... |
@stfnzl Also have 200+ isolated tests that run in parallel. But I noticed that the browser can crash even on 1-5 specs at the very beginning of the run. |
@stfnzl - I have around 150 tests running, and it always seems to fail at the last spec file. If I skip or remove it, the issue pops up at the new last spec file. Now this happens around 80% of the tests that I have removed cypress test suite from the pipeline for now! |
One thing that i did was to switch to using |
Hey,
Timed out waiting for the browser to connect. Retrying... Has anyone found a solution? |
Experiencing this with Cypress 13.6.0, running tests in Github Actions in docker |
Are here any updates or solutions? @jennifer-shehane @mschile @AtofStryker |
We have gotten some DEBUG logs with more specifics that we're looking into. It looks like this error started around 11.0 in Cypress, but is maybe happening more frequently lately due to some other change. |
OK I am able to reproduce this. Its similar to #28397. The logs provided suggest that the browser is exiting mid run (I don't want to say crash because the exit code is 0). When that happens, we wait for the browser to reconnect up to 3 attempts. In this case though, since the browser closed, we closed the CRI client as well and we are able to successfully relaunch the browser, expecting the CRI client to be there, but its not so we get this error. I can reproduce it with this branch against this test suite. I will start exploring solutions shortly... |
Current behavior
Sometimes when running tests (in CD, in docker), cypress simply fails.
We see:
And then
cypress.run
returns:Notes:
--quiet
Desired behavior
tests to run without crashing (or some indication of what is being done incorrectly)
Test code to reproduce
unsure how to reliably reproduce. most projects run fine most of the time.
Cypress Version
12.17.3
Node version
16.20.0
Operating System
Linux / docker
Debug Logs
No response
Other
Looks like the same problem as #27241 and #24650
The text was updated successfully, but these errors were encountered: