Cypress 6.3.0 Fails to exit if connecting to Chrome falls back to TCP

[rpong]

Current behavior

Cypress 6.3.0 Running in Headless Mode, set to Chrome Browser does not EXIT after the tests are done, if the connection falls back to TCP, showing this in any part of the test.

Timed out waiting for the browser to connect. Retrying...
Warning: Cypress failed to connect to Chrome via stdio after 1 minute, 0 seconds. Falling back to TCP...
Connecting to Chrome via TCP was successful, continuing with tests

Additional Information:

• We have to run "killall -9 chrome" for the Cypress to exit, if the tests all passed, it does return a success status when doing this. So it is likely an issue with Cypress during termination.

• If there are retries in the test, which should have otherwise passed due to retry, the retry is not honored, and the test is reported as failed

• This only happens in our AWS EC2 Linux Ubuntu 20.04, it DOES NOT happen in our Mac Mini environment, maybe because the Chrome TCP Fallback does not happen at all in our Mac-Mini Server.

Desired behavior

Cypress 6.3.0 Running in Headless Mode, set to Chrome Browser SHOULD EXIT after the tests are done even if the connection falls back to TCP

Test code to reproduce

This happens on any occasion that this notice appears:

Timed out waiting for the browser to connect. Retrying...
Warning: Cypress failed to connect to Chrome via stdio after 1 minute, 0 seconds. Falling back to TCP...
Connecting to Chrome via TCP was successful, continuing with tests

Versions

6.3.0

[SimulatedGREG]

I can confirm the same issue with GitHub Actions, using ubuntu-18.04. Our tests are also running in headless mode against Chrome. We also were using [email protected].

I can't link to the run because it is in a private repository. Hope this helps and gets resolved soon 🙂. Our internal systems unfortunately hit our usage limit very quickly because of this problem. Our normal 5 minutes runs turned into 4-6 hours runs 🙃.

[jalal246]

Have the same issue: https://github.com/jalal246/dflex/runs/1779823466?check_suite_focus=true with an error "Error: Could not find Cypress test run results"

[geremy22]

Having the same issue, test are executed twice in my windows 10 notebook with chrome 88:

And apparently running once on gitlab shared runner but with a huge timeout delay. Here's job log

[emilong]

I can also confirm this happening on CircleCI. The change in #14348 looks like it might have caused the trouble, but was reverted in #14819.

Sounds like reverting to v6.2.1 might help for now and the next release will also work?

[jbutko]

Same here, reverting from 6.3.0 to 6.2.0 fixed the problem.

[Ahmed-Abd-El-Ghany]

same over here getting this errror:

Timed out waiting for the browser to connect. Retrying...
Warning: Cypress failed to connect to Chrome via stdio after 1 minute, 0 seconds. Falling back to TCP...
Connecting to Chrome via TCP was successful, continuing with tests.

[giacaglia]

It seems that this was fixed on version 6.4.0: https://github.com/cypress-io/cypress/releases/tag/v6.4.0

Tested it out in our repo and upgrading to 6.4.0 fixed the problem for us

[flotwig]

Closing since this is fixed in 6.4.0. Please open a new issue if you are still experiencing this.