Cypress cy.screenshot() timeout during cypress run

[taylorpreston]

Current behavior:

All of our tests pass locally, but when running the Codeship CI we get errors for a few tests.

The error during Codeship CI builds: CypressError: cy.screenshot() timed out waiting '30000ms' to complete.

Desired behavior:

All tests pass in Codeship CI

Steps to reproduce:

For our app the reproduction is running the ci:codeship command runs which calls cy:record
"cy:record": "cypress run --record --key *key* --config video=false", "ci:codeship": "start-server-and-test start http://localhost:5000 cy:record"

I'm not exactly sure how to reproduce this other than creating a Codeship Basic app and attempting to run tests there. I have seen a few other issues point to a problem with how Cypress and Codeship interact.

Versions

Cypress version: 3.4.1

Sidenote: We are using the cypress-autorecord package, but it doesn't seem like this is involved.

[taylorpreston]

@lleewwiiss We never figured out what was causing this issue. We think it has to do with cypress beginning to run tests on the application before it has finished starting. The errors we received were the first 2-5 tests.

[justinpincar]

Also been getting this on 3.5.0 and 3.6.1.

[tibdex]

I also have this issue with 3.8.1 and Chrome 79 on CircleCI's ubuntu-1604:201903-01 machine. It's not there with Chrome 78 or the embedded version of Electron. It's probably related to #6023.

[jennifer-shehane]

• Can you run Cypress in debug mode mode and print the entire set of logs here?
• Can you provide the machine and machine version they are running into this issue with, that would be appreciated.
• Provide the browser you are running within (Electron, Chrome + version).

I don't think this is related directly to #6023

[leichteckig]

Hello,
I have the same issue starting with 3.8.2 (and above) currently. Cypress 3.8.1 works correctly though.

We're using cypress/included docker image in Gitlab CI and keep getting these error messages:

CypressError: cy.screenshot() timed out waiting '60000ms' to complete.

It won't appear in every test and I can't see a pattern in those fails yet. At the moment, I'm struggling with getting debug mode to run, but I'll give an update as soon as I can provide some logs. I hope this first information can help nevertheless. Thank you in advance for all help, information etc.!

[bgcypressqa]

I can confirm with @leichteckig that this issue is occurring as described:

"... 3.8.2 (and above) currently. Cypress 3.8.1 works correctly though.

We're using cypress/included docker image in Gitlab CI and keep getting these error messages:

CypressError: cy.screenshot() timed out waiting '60000ms' to complete."

Only difference is that I am using Azure DevOps CI and their container services.

[teknologista]

I can alsoI confirm with @leichteckig that this issue is occurring as described.

We are using Gitlab CI with Ubuntu CI runners and your docker image cypress/browsers:node12.14.0-chrome79-ff71

CypressError: cy.screenshot() timed out waiting '60000ms' to complete."

random, masks errors also...It doesn't happen locally on desktop/laptop.

Glad I read through this to figure out downgrading to 3.8.1 would solve the issue.

[Powersource]

I am having some variation on this issue. It was just happening for one specific test. Was running 3.6.1 and upgraded to 3.8.1, didn't help. When running the test locally I could see the real reason that the test was failing (instead of the screenshot timeout like CI was claiming). So for me it was mostly an issue of a bad error message i CI.

[teknologista]

@Powersource exactly what I meant by sometimes it also masks the true reason for the test fail

[alexbjorlig]

I just upgraded Cypress to 4.0.1, and we now started to see tests failing on Github Actions with screenshot() timeout warning 😢

[jennifer-shehane]

Need info

I still have questions that have gone unanswered in this thread that are necessary for investigation.

• What browser are you running? What version of the browser?
• Are you running with --headless flag?
• What machine and machine version are you running?
• Are you calling the cy.screenshot() command directly? Are you using a plugin that calls the cy.screenshot() command?

---

Chrome 79 bug?

There has been some speculation that this may be caused by the Chrome 79 performance bug detailed here: #6023 (comment)

If you are running on Chrome 79, we've released a docker image for Chrome 80 found here: https://github.com/cypress-io/cypress-docker-images/tree/master/browsers/node13.6.0-chrome80-ff72 at cypress/browsers:node13.6.0-chrome80-ff72.

Please try to update to using Chrome 80. If this is related to #6023 it may fix your issue.

[alexbjorlig]

Hi @jennifer-shehane.

Need info

I still have questions that have gone unanswered in this thread that are necessary for investigation.

• What browser are you running? What version of the browser? Chrome 79.0.3945.130
• Are you running with --headless flag? No
• What machine and machine version are you running? ubuntu-16.04
• Are you calling the cy.screenshot() command directly? Are you using a plugin that calls the cy.screenshot() command? no

Chrome 79 bug?

There has been some speculation that this may be caused by the Chrome 79 performance bug detailed here: #6023 (comment)

If you are running on Chrome 79, we've released a docker image for Chrome 80 found here: https://github.com/cypress-io/cypress-docker-images/tree/master/browsers/node13.6.0-chrome80-ff72 at cypress/browsers:node13.6.0-chrome80-ff72.

Please try to update to using Chrome 80. If this is related to #6023 it may fix your issue.

I tried using chrome 80 in my Github actions:

jobs:
  e2eTests:
    runs-on: ubuntu-16.04
    container: cypress/browsers:node13.6.0-chrome80-ff72

Using the above container seems to give errors like this, and all tests fails:

[HPM] Error occurred while trying to proxy request /graphql from localhost:4200 to http://localhost:1337 (ECONNREFUSED) (https://nodejs.org/api/errors.html#errors_common_system_errors)

Our setup is an Angular + Graphql Node.js Express application. Is there something special I need to make this work when running in containers - or do you want me to open that as a separate issue?

But screenshots seems to be working 🔥

[jennifer-shehane]

@alexbjorlig Hmm, I haven't seen the ECONNREFUSED error for proxy requests before. Yeah, I would open a new issue. May be more due to the Node upgrade.

The fact that screenshots work in Chrome 80 is very promising though. Thanks for the update.

[alexbjorlig]

@jennifer-shehane - thanks, I will create a new issue for the ECONNREFUSED.

Update
After looking at my logs, I can see that the problem is that our Node server uses a mongo in-memory server. This package has a problem, when running in docker, as described here.

Is there another way to run Cypress with Chrome80? I tried using runs-on: ubuntu-latest, (where the mongodb memory server works without issues), but here the Chrome version is 79 😢

Final update
My build now works with the Chrome80 container, you can see the details here.

[leichteckig]

Hello there,

A little update: I tried Cypress' docker images with Chrome 80 (Cypress 4.0.0 and newer) as recommended in #6023 (comment) and after a week or so, I don't see any more screenshot related failures until now.

In 3.8.2, there was Chrome 79 installed iirc. So it looks like it was the mentioned Chrome bug for me as well. Thank you so much for your advice! 👍

[jpike88]

Just upgraded to cypress/browsers:node12.16.1-chrome80-ff73 and this has broken my test builds using Codebuild.

[jennifer-shehane]

@rhzs It's not recommended to run Cypress instances in parallel on the same machine - we don't fully support this usage. Is this what you're doing where you have the issue? There are a few other issues that can happen when this is done: #26211 #25470 #19565 There's a bunch more

[saas2813]

We're taking another look into this. Spiking into it. We've looked into a few avenues in the past. It's still incredibly difficult to track down without a reproducible example that triggers it reliably.

Hi, When I was working with Cypress the problem showed up when a test failed on a page that was large enough to take long time to create the screenshot from, e.g. a listing from a database that failed to apply limits, thus the timeout was probably correct but since the reported error was the timeout not the actual assertion-failure that triggered the screenshot the reported failure did not give information.

Sorry, I do not have access to either the code or environment I was working on at the time.
It was quite reproducible, whenever there was a test-failure on a too large page I got the problem.
Since it is a timeout you would probably have an easier time reproducing it on a slow machine, but if you put a few MB of "lorem ipsum" in reasonably large font on a page and an assert-fail in a test for it you should be able to trigger the problem. (As I said a runaway DB-query will do it, and you really want to get "5M records returned when 20 was expected" instead of "Timeout" in that situation.)
I should have mentioned I was running Headless, either locally or on our Jenkins CI.

[Sushmak0603]

Hi @jennifer-shehane
Have we got any fix for this issue cy.screenshot() timed out waiting 30000ms to complete. ??
I am currently using Cypress version 12.14.0
I see this issue only when I run the tests in the docker container and do not see this when I run it locally.

[Sushmak0603]

Hi @jennifer-shehane Have we got any fix for this issue cy.screenshot() timed out waiting 30000ms to complete. ?? I am currently using Cypress version 12.14.0 I see this issue only when I run the tests in the docker container and do not see this when I run it locally.

What worked for me is mentioning video: false, in cypress.config.js file in the module.exports section where e2e is folder containing my feature files.

module.exports = defineConfig({
e2e: {
video: false,

[AlexSdet]

Maybe this will be helpful. I found what was causing this issue on my side. One test was clicking link that opens new tab, and basically leave it hanging, and then next test was always failing withcy.screenshot() timed out waiting 30000ms .. as soon as I removed that link click - no more issues.

@jennifer-shehane I could be wrong, but I think the problem here is when Cypress loses focus on main browser tab or something of that nature.

[shiwantha-lakmal]

@AlexSdet Agree with statment as per my investigation also this issue arise between multi state re-direction.
this might not occure when doing element interaction within same context (page)

[jennifer-shehane]

@AlexSdet Yes, I agree this is certainly some of the cases where this happens. We still haven't had a reproducible example to show this timeout relaibly in this situation either though.

[Dale-777]

@jennifer-shehane we have this same issue with a single test, it occurs infrequently, and the reason it appears to be related to this test is the page under test in-particular is highly complex and no doubt is heavy to load & render, so until you have a way to simulate that you will not be able to reproduce this.

For us this error occurs in a feature file, with 8 scenarios, each loading the same page, so could be a memory issue.

cy.screenshot() timed out waiting 30000ms to complete.

Because this error occurred during a after each hook we are skipping all of the remaining tests.[Learn more](https://on.cypress.io/screenshot)
View stack trace
CypressError: `cy.screenshot()` timed out waiting `30000ms` to complete.

Because this error occurred during a `after each` hook we are skipping all of the remaining tests.
    at https://XXXX.com/__cypress/runner/cypress_runner.js:134337:73
    at tryCatcher (https://XXXX.com/__cypress/runner/cypress_runner.js:1807:23)

[Tathos20]

We are running multiple feature files in Azure pipelines. We see this issue always at the first feature file. All of the others are okay. Hope this information hepls.

[eschutho]

We're able to reproduce this consistently in Apache Superset (open source). Here's a PR that shows the E2E CI failures and the test output. The screenshot timeout errors seem to be limited to these code changes, too, but they pass when running Cypress locally. CI is running Chrome 119 on Ubuntu - 20.04.

[jennifer-shehane]

@eschutho Thanks for the repo! Any thoughts on updating to latest Cypress within those tests?

[jennifer-shehane]

@eschutho Could you give the minimal instructions to get this up and running with Cypress tests? I tried to follow the contributing guidelines and am still running into:

(venv)  superset db upgrade
zsh: command not found: superset

Also I get this error when running

pip install -e .

[eschutho]

@eschutho Thanks for the repo! Any thoughts on updating to latest Cypress within those tests?

Hi, @jennifer-shehane yes, we're a little behind in our updates, but we are planning to upgrade this year.

Could you give the minimal instructions to get this up and running with Cypress tests?

You can use the make commands. make superset should install and build and make flask-app for backend make node-app for webpack. Once you have the app running, you can build/run cypress with:
make build-cypress and make open-cypress 9000

If you run into any issues with the make commands, it looks like with where you are currently, you'll need to run pip install -r requirements/local.txt and then follow the rest of the steps.

Alternatively there's a docker image that you can use. These are the instructions for running with Docker. https://github.com/apache/superset/blob/master/CONTRIBUTING.md?plain=1#L973

Happy to help with any other setup questions for reproducing.

[jennifer-shehane]

@eschutho make superset is failing and the docker image exits also. I'll need an easier example to run since this is now taking significant time to run.

[droca]

We were facing this issue as well, only when running the tests on CI (Browserstack) and not all the time. These are our conclusions:

• The cause of this issue was that some of our tests where clicking on buttons and links that were opening new tabs. We didn't do anything on the new tabs and it was not having any effect on the e2e tests running locally.

• The 'solution' we applied was to 'hack' a bit the behaviour of the application under test to avoid the links / buttons from opening a new tab. We did it with this code on the appropriate place:

Cypress.$(element).on('click', e => {
  e.preventDefault()
})

As a caveat, this solution only works for the regular elements / buttons that contain an href, but it doesn't with the ones that are using the onClick function to redirect (like with a react push or something like that)

[jennifer-shehane]

@droca I was able to recreate this situation. Only within the Chrome browser. This can be recreated with cypress open and cypress run.

test.js

it('click on new tab', () => {
  cy.visit('index.html')
  cy.get('a').click().should('have.attr', 'foo')
})

index.html

<html>
  <script>
  </script>
<body>
  <a target="_blank" href="new.html">Click me</a>
</body>
</html>

new.html

<html>
</html>

[cypress-bot]

Released in 13.7.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v13.7.0, please open a new issue.