cypress: Cypress 3.4.0 hangs in CI with Chrome 75

Current behavior:

A test suite that runs correctly in CI using Chrome 73 is now hanging after using Chrome 75.

We have a suite of tests that has been working in CI builds using Chrome 73, and works locally using Chrome 75 and cypress open. When we upgrade to use the cypress/browsers:node10.11.0-chrome75 Docker image, the test runs started to hang after a couple of minutes. There’s no distinct pattern, sometimes it gets through 5 specs, sometimes 7, 10, etc (i.e. I don’t believe it’s a problem with a specific test).

Desired behavior:

Run through the whole suite of tests.

Steps to reproduce: (app code and test code)

This is testing an Angular application. In CI, we are using a Docker image based on cypress/browsers: FROM cypress/browsers:node10.11.0-chrome75, with browser set to chrome and headless mode turned on.

We are using cypress-failed-log and cypress-skip-and-only-ui` plugins. We use the standard spec reporter.

I turned DEBUG logs on and captured the logs from the failing run here: https://gist.github.com/rpd10/5f5522a3b76f79b1e952b81b36411e06

If it helps, I can attach partial DEBUG logs from a successful Chrome 73 run.

Versions

Cypress 3.4.0 and 3.3.2. Chrome 75 (FROM cypress/browsers:node10.11.0-chrome75). GitLab 11.11.5.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 16
  • Comments: 18 (3 by maintainers)

Most upvoted comments

I face this problem too on Chrome 80.0.3987.100-1, node10.16.0-chrome77, and cypress 4.0.1. But it’s working fine on Cypress 3.8.3 @jennifer-shehane : is it a regression bug?

I face this problem too. Now I can run both chrome 73 and 74 in docker but all chrome 75 (all node versions) it is hang.

Finally, I get a workaround from my friend to be able to run on chrome docker version > 74 with this https://github.com/cypress-io/cypress/issues/350#issuecomment-503231128 I have tried with node10.16.0-chrome77, and it works properly. (With Cypress 3.4.1) No more hang anymore. image

so we split the tests into two files

Yes, it helps us as well. When test suite execution time is more than 5-6 minutes - usually it hangs. (Your “critical execution time” may be above 6 min as we have a lot of additional logging in background in our case) The problem is that as cypress return no errors in case browser crashes or hangs - pipeline (Concourse CI) with container keep running and should be terminated manually.