-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Cypress unexpectedly and randomly hangs when running tests in CI #1912
Comments
Thank you for posting your logs. This is very helpful. |
Released in |
Thank you so much for this release @brian-mann! You folks are doing amazing work and I'll always be a crazy supporter of this project <3 from the @sendwithus team |
We still see this issue happening to our builds with
And then it stops, and the build is killed by CircleCI with "Too long with no output (exceeded 10m0s)". Same as for the author of this issue, it's not obvious how to reproduce it, sometimes it hangs, sometimes it doesn't. @brian-mann @jennifer-shehane do you want to reopen this issue, or should it be a new one? |
@ikornienko The log you provided seems to suggest it's the very same issue we're still having on |
I haven't had time to post back here after running some tests on |
@brandonb927 @kamituel @ikornienko We've investigated this - and we're still unsure where this could be happening. We fixed the state stuff in Currently we we cannot reproduce this locally or in CI, so we'll release |
FWIW, we're having the same issue on Buildkite, with docker containers as well ( Using working test
not working test
I will also try and update logs with |
We are also having random errors in travis CI (with cypress 3.0.3). This is the last part of the trace (including the last successful test and the one that never ends):
|
It appears 3.1.0 was released today, going to test it out to see if this squashes the bug here once and for all! |
@brandonb927 Definitely do. It fixed this issue for us. Yay! |
I have a high degree of confidence that we can finally upgrade to 3.1.0 from 2.1.0, upgrading today. |
I'm still seeing the bug on 3.1.0 |
I completely forgot to come back to this and make a note that the 3.1.0 release definitely fixed this finally and we've been running it on our Jenkins nodes for some time now with no issues (well, none related to this issue at least). |
Running |
Same here, haven't seen this one popping up in the last weeks 👍 |
I am getting in on Its not reproducble in "dev" mode only "run". @brian-mann i hope it helps you to write repro. EDIT: |
@krzkaczor that sounds like normal behaviour for Cypress and isn’t related to this original issue. |
Current behavior:
We have tests running in Jenkins using docker and docker-compose for running micro-services. Many containers spin up and one is used for our app UI, but these are not the problem.
Since upgrading to Cypress 3.0.1, we've been noticing that random builds just stall out and never complete. As a result of this we've had to instate a 30minute timeout on Jenkins jobs. There are no errors visible in the console output so its hard to see what is happening. The exact same codebase, less some changes to upgrade to Cypress 3, worked on Cypress 2.1.0 perfectly fine up until we upgraded. Like this issue, it will run an random number of specs and stall. Everything runs fine using the headed mode, it seems to only affect headless mode.
Below is some log output from invoking Cypress with
DEBUG=cypress:* ./node_modules/.bin/cypress run --env configFile=ci --reporter mocha-multi-reporters --reporter-options configFile=cypress/config/reporters.json
Desired behavior:
All tests to run and output correct information regardless of fail or passing
Steps to reproduce:
It's bizarre, I'm not quite sure how to reproduce it reliably as it seems completely random, and only happens about 30% of the time.
NOTE: I cannot recreate a reproducible test case with https://github.com/cypress-io/cypress-test-tiny as it just passes ever single run using Jenkins.
Versions
Cypress 3.0.1 + cypress/base:10 docker image
Jenkins 2.89.3
The text was updated successfully, but these errors were encountered: