Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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

See original GitHub issue

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

Issue Analytics

State:
Created 3 years ago
Reactions:49
Comments:8 (1 by maintainers)

Top GitHub Comments

6reactions

giacagliacommented, Feb 2, 2021

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

4reactions

SimulatedGREGcommented, Jan 26, 2021

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 node@12.13.1.

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 🙃.

Top Results From Across the Web

Changelog - Cypress Documentation

Instead of using stdio and then falling back to TCP, Cypress now only uses TCP to try to connect to Chrome DevTools Protocol....

Cypress failed to make a connection to the Chrome DevTools ...

Cypress failed to make a connection to the Chrome DevTools Protocol: ECONNREFUSED at TCPConnectWrap. afterConnect - Stack Overflow. Stack ...

cypress: Versions - Openbase

Instead of using stdio and then falling back to TCP, Cypress now only uses TCP to try to connect to Chrome DevTools Protocol....

Release/5/5.1 - RTEMS Project

#2775: ARM CP15 arm_cp15_set_translation_table_entries fails if TTB in read-only ... to `rtemsrtl_base_globals' collect2: error: ld returned 1 exit status.

Recommended Beta update for SUSE Manager Client Tools

Update to version 7.4.2: * Make Datetime local (No date if today) ... (#30823) * bump cypress to 6.3.0 (#30644) (#30819) * Expressions: ......