Cypress verification fails randomly during Docker CI
See original GitHub issueMaking a new post as requested here: https://github.com/cypress-io/cypress/issues/4624#issuecomment-570129903
We are running Cypress 3.7.0 and we see this problem (failed verification) periodically. We run Cypress in Docker containers as part of our CI and sometimes they may be underpowered, as has been noted in other issues. Unfortunately the logs don’t really provide any color here:
15:51:06 [23:51:01] Verifying Cypress can run /home/jenkins/.cache/Cypress/3.7.0/Cypress [started]
15:51:38 [23:51:35] Verifying Cypress can run /home/jenkins/.cache/Cypress/3.7.0/Cypress [failed]
It would appear that 30 seconds is sometimes just not enough time. Is there some way we can set this timeout in our Cypress config? Or a way we can disable this test altogether? Either of these would be much more preferable than Cypress failing, which wastes a lot of our time because our tasks have to be restarted.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:23 (4 by maintainers)
Top Results From Across the Web
Troubleshooting | Cypress Documentation
There are times when you will encounter errors or unexpected behavior with Cypress itself. In this situation, we recommend checking these support.
Read more >Unable to run Cypress Test with Gitlab CI - Stack Overflow
I am integrating Cypress Test with Gitlab CI. But when I am running the pipeline, I came up with these issues. Please find...
Read more >Cypress Tips and Tricks - Gleb Bahmutov
I have configured our GitLab CI to keep artifacts from failed test runs for 1 week, while keeping videos from successful test runs...
Read more >cypress-io/cypress - Gitter
@rajkumars82. Hi anyone facing issues in gitlab-ci on installing cypress 3.6.0 ... During my test I get a verification number (random) by clicking...
Read more >agoldis/sorry-cypress-dashboard - Docker Image
run cypress tests in parallel without dashboard; upload failure ... multiple instances of cypress run --parallel --record --key xxx --ci-build-id <buildId> ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We had the same problem 90% of the time. Probably due to the CI runner (network problem?) The trick was to change the timeout const in the CI script:
Same here, Cypress 3.8.3 running docker image
cypress/browsers:node10.16.3-chrome80-ff73
in Gitlab CI