cypress: Error: could not find CRI target

Current behavior:

Error: could not find CRI target when running on chrome

Note : Tests run successfully in electron and firefox

Desired behavior:

Tests should run in Chome browser

Test code to reproduce

Run Integration/example tests using command

 node_modules\.bin\cypress run  --browser chrome

could not find CRI target
Error: could not find CRI target
    at lazyAssLogic (C:\Users\nidhi\AppData\Local\Cypress\Cache\4.0.2\Cypress\resources\app\packages\server\node_modules\lazy-ass\index.js:110:14)
    at lazyAss (C:\Users\nidhi\AppData\Local\Cypress\Cache\4.0.2\Cypress\resources\app\packages\server\node_modules\lazy-ass\index.js:115:28)
    at findStartPage (C:\Users\nidhi\AppData\Local\Cypress\Cache\4.0.2\Cypress\resources\app\packages\server\lib\browsers\protocol.js:55:3)
    at processTicksAndRejections (internal/process/task_queues.js:85:5)

Versions

Cypress: 4.0.2 Browser: Chrome 80 Windows 10

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 17 (8 by maintainers)

Commits related to this issue

Handle more CDP connection errors Moving this .catch statement to clean up errors, for example, the error that occurs in #6518 will now be wrapped by this. — committed to cypress-io/cypress by flotwig 4 years ago

Most upvoted comments

I saw this issue in last 2 weeks twice with Cypress v9.7.0 and Firefox v101 in CI. Is this thread still up to date? Are there any other issues you can recommend for solving this issue? I already checked out #7450, but it seems to be mainly about Chrome.

frontendflorian on Jun 24, 2022

This issue is occurring for me when I am running more than once spec file in chrome headless mode.

if I run the specs individually, the issue does not occur.

symon-skelly on May 29, 2020