Error: could not find CRI target (Cypress 4.6.0)

[stevejefferies]

Current behavior:

cypress run fails with the following error on Chrome:

Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.

This usually indicates there was a problem opening the Chrome browser.

The CDP port requested was 26359.

Error details:

Error: could not find CRI target
    at lazyAssLogic (C:\Users\user\AppData\Local\Cypress\Cache\4.6.0\Cypress\resources\app\packages\server\node_modules\lazy-ass\index.js:110:14)
    at Object.lazyAss (C:\Users\user\AppData\Local\Cypress\Cache\4.6.0\Cypress\resources\app\packages\server\node_modules\lazy-ass\index.js:115:28)
    at findStartPage (C:\Users\user\AppData\Local\Cypress\Cache\4.6.0\Cypress\resources\app\packages\server\lib\browsers\protocol.js:56:23)

Full log is also attached.

Note that this doesn't appear to be 100% consistent. With the below example I am seeing this maybe 25% of the time.

We had previously observed this before, and upgraded to both 3.8.3 as a result of: #6053

Then more recently, upgraded to 4.6.0 as a result of: #6518

Still observing on 4.6.0 as below though

Desired behavior:

Execution should not fail in this manner.

Test code to reproduce

1. Clone https://github.com/stevejefferies/cypress-test-tiny
2. Run cypress:run as defined in package.json e.g. npm run cypress:run

Versions

Cypress: 4.6.0
Browser: Chrome 83
OS: Windows 10

Debug Log

debug_log.txt

[jennifer-shehane]

Oh, this is sad, we thought the increased timeout would help. Where are you running these tests when this typically happens? Locally? In a CI?

Running Chrome 83 headless

This happens at the very beginning of running the next spec (after the first spec has finished running), which is identical to #6518 We'll likely reopen that issue if others verify the fix did not work for them.

[stevejefferies]

Unfortunately both observed locally and in a CI environment

[stevejefferies]

For reference its more typically observed on running the second (or subsequent) specs. But has been observed on running the first spec on occasion.

[jareqpl]

I have observed the same thing today. This started to occur after chrome update from 81 to 83.

[SonaliQA]

I also found the same error as @stevejefferies found
It working on cypress open UI but not able to run on the headless browser and not in CI environment also

[yetimaan]

We are also seeing this issue in CI. Chrome Version 83.0.4103.61 headless with Cypress 3.8.3 in Azure Devops Windows CMD agent. We also got same error with latest Cypress 4.6.0. In the meantime, we're using Electron 78 in CI - which is working. I do not have this issue locally on MacOSX Chrome Version 83.0.4103.61.

[mikirobles]

This is happening in my github actions flow in a very inconsistent basis. Tried with the latest cypress version and also 3.8.3.

Workflow:

name: PR - Testing

on: [pull_request]

jobs:
  cypress-run:
    name: Cypress
    runs-on: ubuntu-16.04
    steps:
      - name: Checkout
        uses: actions/checkout@v1
      - uses: bahmutov/npm-install@v1
        with:
          useLockFile: false
      - name: Run tests
        uses: cypress-io/github-action@v1
        with:
          install: false
          browser: chrome
          start: npm run start-http
          wait-on: 'http://localhost:3000'
          config: baseUrl=http://localhost:3000,defaultCommandTimeout=10000

package.json:

    "cypress": "3.8.3", // Also happens with 4.5.0

Also note it's running with Chrome 81

[flotwig]

If it's happening with Chrome 83, this could be the cause: #7433

[Sumanth1703]

I also found the same error as @stevejefferies found

I am facing this issue for both chrome and edge browser, It's working on cypress open UI but not able to run on the headless browser and not in CI environment also.

Any update on this issue ?

[PetMou]

Since chrome 83 was installed we also have this issue.

2020-05-29T10:15:14.1447528Z Failed to connect to Chrome, retrying in 1 second (attempt 60/62)
2020-05-29T10:15:14.1447578Z Failed to connect to Chrome, retrying in 1 second (attempt 61/62)
2020-05-29T10:15:14.1447611Z Failed to connect to Chrome, retrying in 1 second (attempt 62/62)
2020-05-29T10:15:14.1447646Z Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.
2020-05-29T10:15:14.1447669Z 
2020-05-29T10:15:14.1447719Z This usually indicates there was a problem opening the Chrome browser.
2020-05-29T10:15:14.1447827Z 
2020-05-29T10:15:14.1447858Z The CDP port requested was 52137.
2020-05-29T10:15:14.1447878Z 
2020-05-29T10:15:14.1447906Z Error details:
2020-05-29T10:15:14.1447941Z 
2020-05-29T10:15:14.1447970Z Error: could not find CRI target
2020-05-29T10:15:14.1448012Z     at lazyAssLogic (C:\Users\ZMSAAZU002\AppData\Local\Cypress\Cache\4.7.0\Cypress\resources\app\packages\server\node_modules\lazy-ass\index.js:110:14)
2020-05-29T10:15:14.1448064Z     at Object.lazyAss (C:\Users\ZMSAAZU002\AppData\Local\Cypress\Cache\4.7.0\Cypress\resources\app\packages\server\node_modules\lazy-ass\index.js:115:28)
2020-05-29T10:15:14.1448121Z     at findStartPage (C:\Users\ZMSAAZU002\AppData\Local\Cypress\Cache\4.7.0\Cypress\resources\app\packages\server\lib\browsers\protocol.js:56:23)

[thdepauw]

Any update on this issue?

We are also facing this issue on our local machines (win 10 - chrome 83.0.4103.61) when running headless.
Our CI on Azure DevOps hasn't encountered this issue yet since it is still running on chrome 81.

The workaround of @Diald to run on elektron is not an option for us.