Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Execution time increased drastically after upgrading from 8.3.0 to 8.6.0

See original GitHub issue

Current behavior

After upgrading cypress from 8.3.0 to 8.6.0, execution time of our tests (same amount of tests/suits) increased by ~10 min (almost doubled the initial time to execute). Current execution results (version 8.6.0):

Desired behavior

We’d expect, that execution time stays the same or gets lower with cypress update, not increase almost two times. Previous execution results (version 8.3.0):

Test code to reproduce

yarn upgrade cypress@8.6.0

Cypress Version

8.6.0

Other

Currently had to revert back to 8.3.0, because otherwise builds time out (due to the 30m aws-amplify build timeout setting).

Issue Analytics

State:
Created 2 years ago
Reactions:30
Comments:41 (9 by maintainers)

Top GitHub Comments

16reactions

lszmit-nmcommented, Jun 2, 2022

We have observed the exact same problem moving from 8.3 to 8.6. Our test pipeline of 136 tests in 22 specs had its runtime escalate from ~30 minutes to over 2h (we’re using Chrome, not Electron). Disabling video recording made a difference, but moving back to 8.3 had the most impact.

More follow-up in terms of performance regressions since 8.3. Our current pipeline runs on GitLab.com shared runners, and uses the node16.14.0-slim-chrome99-ff97 image as base.

We’ve managed to stabilise the runtime for our 28 specs (147 tests) around the 30 minute mark with the 9.x release by disabling videos, disabling test recording in dashboard, disabling parallel runs and switching from Electron to Chrome.

Today, as a test I’ve moved the entire setup to Cypress 10.0.1. Same base image, same specs, same config, just newer Cypress release. It (barely) managed to execute 12 specs before the 60 minute runtime limit killed the job. It took 16 minutes on a dev laptop.

The way I see it, something has dramatically changed in how Cypress behaves in CI/headless environments, running inside a docker container, since the 8.3 release. It’s really becoming unusable at this point.

11reactions

helenaritsoncommented, Nov 15, 2021

We are also experiencing the same issue - recent versions are much slower(both locally and in CI) and we are stuck on version 6.6.0 First biggest time difference was upgrading to 7.7.0 where test execution time jumped from ~37 to ~81 sec: