Skip to content
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

Closed
bsodmike opened this issue Feb 19, 2020 · 7 comments

Comments

@bsodmike
Copy link

bsodmike commented Feb 19, 2020

Current behavior:

We had no issues with chromium 79, however, now with chromium 80 or Chrome-beta chrome-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

  • Cypress 3.3.2
  • Chromium 80
  • Chrome (beta) 81
@bsodmike bsodmike changed the title Chrome 80/81: "The automation client disconnected. Cannot continue running tests." Chrome-beta 81: "The automation client disconnected. Cannot continue running tests." Feb 19, 2020
@bsodmike
Copy link
Author

Seeing #6023 I'm not entirely sure it's worth doing a manual install of Chromium 79

@jennifer-shehane
Copy link
Member

We have a PR open to test against Chrome 80 that may potentially find some issues. #6428 cc @flotwig

@dthomason
Copy link

Also seeing this issue in CI with Chrome 80

@bsodmike
Copy link
Author

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 Timed out waiting for the browser to connect. Retrying....

================================================================================

  (Run Starting)

  ┌────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:  3.3.2                                                            │
  │ Browser:  Custom Chromium 78                                               │
  │ Specs:    24 found (active_members/change_status_spec.js, active_members/… │
  │ Searche…  spec/cypress/integration/active_members/change_status_spec.js, … │
  └────────────────────────────────────────────────────────────────────────────┘


────────────────────────────────────────────────────────────────────────────────

  Running: active_members/change_status_spec.js...                    (1 of 24) 

Warning: Cypress can only record videos when using the built in 'electron' browser.

You have set the browser to: 'chromium'

A video will not be recorded when using this browser.

Timed out waiting for the browser to connect. Retrying...
The automation client disconnected. Cannot continue running tests.

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:

@bsodmike
Copy link
Author

@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.

@bsodmike
Copy link
Author

bsodmike commented Feb 25, 2020

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 │
│ Browser: Chromium 80

@jennifer-shehane
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants