-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: could not find CRI target / Failed to connect to Chrome #6053
Error: could not find CRI target / Failed to connect to Chrome #6053
Comments
I also run into this issue but not always. Mostly if I start "cypress run" twice in a row.The issur started since the update from 3.8.0 to the new patch release |
Same for me, the build for PR was passing, but when I merged a PR into the |
Confirming the flakiness of the issue, just pushed another commit into Just to clarify that it's most probably not caching issue as I'm not using any caching of node_modules. GitHub actions isn't caching anything by default and https://github.com/actions/cache isn't used in the linked project. |
re-enable when cypress-io/cypress#6053 is fixed
re-enable when cypress-io/cypress#6053 is fixed
Could you run Cypress in debug mode mode and print the entire set of logs here? |
Just fixed this issue with the command below to run locally at least:
|
I can't run Cypress in any mode, including the debugging mode. The failure is happening before Cypress is started because in order to start Cypress needs to connect to the browser and the connection stage is failing: See the whole output here: https://github.com/sweetalert2/sweetalert2/runs/365206238 |
@limonte Cypress will print logs at the very beginning of |
Tail end of logs for me where I see the error. |
Can confirm the error is flaky. After trying a few times it will eventually run. |
Update: this was a coincidence of timing. We are seeing this error in about 1/2 of our test runs. |
Possibly related to #5960 |
Downgrading to Cypress 3.8.0 solved the issue for me, look like this issue introduced in the latest version (3.8.1) |
This happened for me in 3.8.1 when using the Cypress Module API (
But 3.8.0 has #5949 so you still won't be able to use Chrome headless if you downgrade. |
Also having this issue... making a post so I can follow and see if this will be resolved. I am in the same boat where 1/2 of the tests fail with this error. |
Not quite sure, but I have the impression that the issue appears when another Chrome session is active during the test run. When I close chrome and keep it closed during a 'cypress run', everything runs fine (Windows 10). |
I'm also getting this error occasionally. (Running within a Docker container, so I don't think it's due to multiple Chrome sessions being open, unless from a previous test suite.) |
@hunghau there's the "Subscribe" button for that purpose:
|
You are right @sebinsua. I also got the issue in our OpenShift Jenkins pipeline (Linux) |
I am having this issue after update to 3.8.1, any news? |
I'm locally getting this error, randomly. Sometimes it runs fine, sometimes it doesn't. It can happen at any given time, but always between switching spec files, never within a test (so it either boots or not, basically). |
I am getting the same error while running headless tests (it happens randomly while spec file is switching to another one) |
Ok, got the error on Mac
Then it failed to connect The terminal is showing
The Chrome Canary looks like this BUT I can query the list of connection targets on port 51298
which does include Then there was the following observation:
|
With above in mind, I found a way to recreate the problem as follows:
After 3-6 tries I get the "cannot find CRI target" message, the following terminal output in Cypress
But then I can in another tab do the following (I am using same port that
So it seems to me |
I have added a retry to
|
@bahmutov Since you've narrowed it down to Mac Canary, thought you may revisit the theory of this being caused by this Mac Chrome bug https://bugs.chromium.org/p/chromium/issues/detail?id=994085 which was initially suspected as the cause of this error in NeuraLegion/cypress-har-generator#17 (comment) |
Hi @jennifer-shehane this has been happening for me on GitHub Actions on Ubuntu latest (and on also on my local Mac) so I'm not sure it is Mac specific. Also - only happening in Chrome headless mode and only when changing specs (never when running a single spec). I've noticed the Chrome instance stays up and I have to kill all instances to get the tests to work again at all. |
I don't see how disabling GPU affects it, but who knows? It could be a combination of headless Chrome and environment. Just to see if we can recreate this I have added headless Chrome test runs to our repos
|
Also added Chrome + Chrome headless test runs inside GitHub Actions in cypress-io/cypress-example-kitchensink#346 to observe |
The code for this is done in cypress-io/cypress#6133, but has yet to be released. |
I'm to the point that I cannot run cypress on my mac, because I get this error so constantly. Any idea when this will be released? downgrading cypress didn't fix it. |
@xdumaine We release every 2 weeks - so this should be released today (1/24/20) barring no complications with the release. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior:
cypress run --headless --browser chrome
is failing in GitHub Actions with this error:Link to the failing build: https://github.com/sweetalert2/sweetalert2/runs/365206238
Steps to reproduce: (app code and test code)
Here's the GitHub Actions configuration: https://github.com/sweetalert2/sweetalert2/blob/master/.github/workflows/coverage.yml
The
cy:run
command is defined here: https://github.com/sweetalert2/sweetalert2/blob/master/package.json#L98Versions
Cypress: 3.8.1
Operating System: Ubuntu 18.04
The text was updated successfully, but these errors were encountered: