Chrome headless fails with "Error: could not find CRI target"

[marmite22]

Current behavior:

I'm running the command node_modules/.bin/cypress run -b chrome --headless -s './cypress/integration/003_website_settings/01_init.js' (the path to the test is not relevant)

I get the error Error: could not find CRI target

I have tried on my Macbook and also on our CI server (Ubuntu).

Running with debug env variable shows the following

I think the relevant part is:

  cypress:network:connect received error on connect, retrying { iteration: 0, delay: 100, err: Error: connect ECONNREFUSED 127.0.0.1:56319     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1056:14) { errno: 'ECONNREFUSED', code: 'ECONNREFUSED', syscall: 'connect', address: '127.0.0.1', port: 56319 } } +250ms
  cypress:network:connect successfully connected { opts: { getDelayMsForRetry: [Function: _getDelayMsForRetry], port: 56319 }, iteration: 1 } +104ms
  cypress:server:protocol CRI.List on port 56319 +106ms
  cypress:server:protocol CRI List { numTargets: 0, targets: [] } +37ms
  cypress:server:cypress exiting with err Error: could not find CRI target

Desired behavior:

I would like the test to run in a headless Chrome instance.

Steps to reproduce: (app code and test code)

Install and run cypress with a test (the contents of the test seem to be irrelevant as it fails before it starts running the test.

Versions

Chrome Version 79.0.3945.79
Cypress Version 3.8.0

[jennifer-shehane]

Possibly related: NeuraLegion/cypress-har-generator#17

From that issue, it may be related to a Chrome issue on macOS (https://bugs.chromium.org/p/chromium/issues/detail?id=994085).

Do you have any plugins or other setup? Maybe tapping into Chrome remote debugger?

[marmite22]

Thank you, removing my node modules folder and re-installing so that I got the up to date version of that dependency has fixed the issue.

[WinstonN]

I can confirm that I had to remove 3.8.1 cache folder, as well as my node_modules folder, and reinstall from scratch. After that the error went away

[jonsmithers]

I might be imagining things, but after fiddling with re-installing stuff, it seems to go away for a few runs, and then it comes back with the next yarn install. It seems very fickle. That might just be coming from yarn. I have no idea. I'm already playing around with yarn cache clean and yarn install --cache-folder=~/.custom-yarn-cache and not getting consistent behavior...

[erezrokah]

@jonsmithers I'm experiencing the same issue. yarn cache clean, removing node modules and cleaning Cypress cache didn't work. Very inconsistent.

[SharanyaRK]

I could experience the same while running in docker containers.

[jennifer-shehane]

If you're experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run since the original issue was resolved. There may be a specific edge case with the issue that we need more detail to fix.

[jennifer-shehane]

Duplicate of #6053