cypress: Cypress verification fails randomly during Docker CI

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

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 6
Comments: 24 (5 by maintainers)

Commits related to this issue

Add CYPRESS_VERIFY_TIMEOUT On slow machines (esp. with a virus checker installed), running install and verify can timeout. People are working around this by editing this file as part of a script -... — committed to lukeapage/cypress by lukeapage 3 years ago

Most upvoted comments

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:

sed -i ‘s/const VERIFY_TEST_RUNNER_TIMEOUT_MS.*;/const VERIFY_TEST_RUNNER_TIMEOUT_MS = 100000;/g’ node_modules/cypress/lib/tasks/verify.js

npx cypress verify

maximenathan on Jun 15, 2021

Same here, Cypress 3.8.3 running docker image cypress/browsers:node10.16.3-chrome80-ff73 in Gitlab CI

Sebosek on May 26, 2020