-
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
Chrome-beta 81: "The automation client disconnected. Cannot continue running tests." #6501
Comments
Seeing #6023 I'm not entirely sure it's worth doing a manual install of Chromium 79 |
Also seeing this issue in CI with Chrome 80 |
Hey @jennifer-shehane Thanks for the feedback! I took a deeper look at the issue by building Chromium 78.0.3904.130 as I wasn't sure exactly which build "broke" between 79 and 80/81. This provided a bit more insight with the additional detail of
Here's the full log with debugging turned on. I also took a look at the fixes you were posting at #6428 and interestingly there seems to be some issue with https-proxying going on here as well. Chromium seems to be:
|
@jennifer-shehane I wanted to verify behaviour with Chromium 80 (default Ubuntu install) and Cypress 3.3.2; here's the full log (see my comment in the at the bottom of the linked Gist). The timeout behaviour does not present itself in this case. Hope this will help you diagnose the issue further. |
Upgrading Cypress has resolved this issue. However, @jennifer-shehane I noticed when reviewing the debug logs, those strange errors were presenting themselves (those cryptic URLs in my gist). │ Cypress: 4.0.2 │ |
Closing as resolved. 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. There may be a specific edge case with the issue that we need more detail to fix. |
Current behavior:
We had no issues with
chromium 79
, however, now withchromium 80
or Chrome-betachrome-81
, we get the following error:Error "The automation client disconnected. Cannot continue running tests."
Desired behavior:
As with
chromium 79
, specs should run just fine.Versions
The text was updated successfully, but these errors were encountered: