-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Cypress can't connect to the browser when running Cypress 6.3 #14809
Comments
Also seeing this |
This warning message about 'Timed out waiting for the browser to connect' is irrelevant to the error that is causing the test run to fail. The TCP connection was successful, so continued with your tests normally. Then real error was encountered
This is throwing from mocha-junit-reporter. Are you using this reported in your tests? Can you provide a reproducible example. |
We are using the standard reporter, so that is mocha-junit-reporter. The reporter does not work when Cypress does not connect to the browser, and that causes the mocha-junit-reporter to fail. So there are 2 issues here:
So what I think is happening is that Cypress 6.3 has a problem connecting to the browser in some instances and the mocha-junit-reporter can't use the results from Cypress when that happens |
@jennifer-shehane That is the same problem as others are seeing here: #14701 |
Seems to be fixed on version 6.4.0: https://github.com/cypress-io/cypress/releases/tag/v6.4.0 Trying it out |
Oh no, I just upgraded to 6.4.0 on my local and now I only have this error. |
This fixed it for me |
Upgrade to 6.4.0 |
We've updated Cypress from version 6.0 to 6.3 and we are consistently getting a problem timing out in our CI machine. We are running Cypress on one of the Circle CI machines and we get the following message causing the response of the tests to fail even though they run:
This has happened when we updated Cypress from
6.1.0
to6.3.0
. This error is intermittent.Current behavior
Seeing the following message when running cypress:
Desired behavior
Just have cypress connect to the browser
Test code to reproduce
We run the command
cypress run --headless --browser chrome
on this docker image: https://circleci.com/developer/images/image/cimg/node with a simple test.We do have the latest version of jest-junit, i.e. version 12.0.0
Versions
Last Cypress version that it was working 6.1.0. We are running on a docker container created from the docker image: https://circleci.com/developer/images/image/cimg/node
The text was updated successfully, but these errors were encountered: