-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Opening 2 instances of Cypress App fails with connection error to Chrome DevTools Protocol #5613
Comments
Maybe the same issue? #5445 Do you use the cypress-log-to-output plugin or set the --remote-debugging-port= manually in an own plugin? |
This is a known issue - if you have 2 instances of Cypress Open, this can happen - although there is something particular about the situation that does not occur on all of our teammates machines that we haven't been able to narrow down. From I can recreate this behavior by doing the following:
My DEBUG logs
Specific logs at time of error toward the end:
|
@jennifer-shehane I only had one instance of Cypress opened when I encountered this issue, but had the Chrome browser opened as well. After I shut down Cypress and Chrome, restarting Cypress does not give me the issue. Sorry I didn't capture the debug log when the error occurred on me when I had only one instance of Cypress opened. I can reliably reproduce the error when I have two instances of Cypress opened. |
In addition, when I changed the CircleCI tests to use Chrome 78, exactly the two tests failed. There should be only one instance of Cypress when these tests were run. https://app.circleci.com/jobs/github/cypress-io/cypress/188912 Here's the information on the redirection test:
Here's the information on the navigation test:
|
@clarmso The issue you talk about in the OP happens, I believe, because Cypress shares a So Chrome #1 launches with And Chrome #2 launches with And because the data dir is the same, Chrome collates the second launch into the first process, and drops the I see 2 ways to fix this:
I like the first option best, because it totally cleans up this experience while still allowing users to install extensions inside Chrome for debugging. Plus, currently, it's a miracle if you can actually get 2 Cypress instances running at once, because they'll fight over the Chrome instance. This would fix that. |
Cypress does not intend to bring up multiple browsers at once (https://docs.cypress.io/guides/references/trade-offs.html#Multiple-browsers-open-at-the-same-time). Should we just prohibit anyone from bringing up multiple instances of Chrome so that we don't have to worry about Cypress fighting over the Chrome instance? |
THIS FIXES THIS PROBLEM!!! by @simisimon in #6540 (comment)_ |
This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided. |
This issue has been closed due to inactivity. |
Current behavior:
The tests
commands/navigation_spec.coffee
ande2e/redirects_specs.coffee
fail on Chrome 78 but pass on Electron.The CLI outputs the following when one of these tests is run:
Here's the error from Cypress:
Here's what CircleCI do (when I had Chrome 78 to run the tests):
https://app.circleci.com/jobs/github/cypress-io/cypress/184452
Desired behavior:
These tests should pass on both Chrome 78 and Electron. These tests used to pass. (They must pass on Chrome 73 because Chrome 73 was used in the CircleCI tests.)
Steps to reproduce: (app code and test code)
cd packages/driver
.npm start
npm run cypress:open
Versions
Cypress 3.6.0
Chrome 78.0.3904.87
MacOS 10.15 Catalina
The text was updated successfully, but these errors were encountered: