cy.task('combineCoverage') timed out after waiting 60000ms getting this error during bitbucket CI build.
See original GitHub issueLogs and screenshots cy.task(‘combineCoverage’) timed out after waiting 60000ms. getting this error a lot during the execution of test cases on bitbucket but locally when the same test cases are executed then it is working fine. The above error is randomly thrown for various test cases.
Versions Version - 3.9.2 Cypress version - 7.3.0
- What is this plugin’s version? If this is NOT the latest released version can you try the latest version, please?
- If the plugin worked before in version X, but stopped after upgrading to version Y, please try the released versions between X and Y to see where the breaking change was.
- What is Cypress version?
- What is your operating system?
- What is the shell?
- What is the Node version?
- What is the NPM version?
- How do you instrument your application? Cypress does not instrument web application code, so you need to do it yourself.
- When running tests, if you open the web application in regular browser, and open DevTools, do you see
window.__coverage__
object? Can you paste a screenshot? - Is there
.nyc_output
folder? Is there.nyc_output/out.json
file. Is it empty? Can you paste at least part of it so we can see the keys and file paths? - Do you have any custom NYC settings in
package.json
(nyc
object) or in other NYC config files - Do you run Cypress tests in a Docker container?
Describe the bug A clear and concise description of what the bug is.
Link to the repo Bugs with a reproducible example, like an open source repo showing the bug, are the most likely to be resolved.
Example
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:17 (4 by maintainers)
Top Results From Across the Web
cypress-io/cypress - Gitter
The response we received from your web server was: 404: Not Found. When using Bitbucket Pipeline? I am stuck in this error and...
Read more >Bitbucket Server commands timeout when trying process ...
This will lead to for example REST requests timings out (so the UI for the commits page will show a 500 error after...
Read more >Problem in creating Cypress code coverage report for E2E tests
The issue I am facing is running all the tests together hangs the system as well as fails due to timeout errors, it...
Read more >Bitbucket Pipelines - Cypress Documentation
What you'll learn How to run Cypress tests with Bitbucket Pipelines as part of CI/CD pipeline How to parallelize Cypress test runs withins...
Read more >Continuous Integration articles
Speed up your tests with optimal test suite parallelisation on your CI. Blog & documentation for Knapsack Pro.
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 FreeTop 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
Top GitHub Comments
I’m facing the same issue as well. How can I provide more information like the number of keys, when running from CI?
I think I have 244 keys and this problem happens on my AWS EC2 T3 Medium (4 GB RAM).
If I
cy.pause()
when running locally and then check the coverage object I get 244, I don’t know if this is relevant, compared to @dane-harnett 's 4500 it’s nothing.This error only happens on CI, never seen it when running it locally.
False positive. I’m still getting those errors again. I’m using Nx for my project management.