When executing a spec which exceeds past 10-15 mins of runtime, the cy.task('dumpEvents') task is timing out on the default 60000ms task timeout. We increased the timeout to 300000ms (5 mins) and set failedTestsOnly: true parameter so only the failed test (which is only a couple mins long) will be stored but we are still getting the same issue.
Expected behavior
The cy.task('dumpEvents') should not timeout for the failed test even if the complete spec file execution exceed 15 mins+ of runtime.
```
# Put your logs below this line
"after each" hook: P for "test":
CypressError: `cy.task('dumpEvents')` timed out after waiting `300000ms`.
https://on.cypress.io/api/task
Because this error occurred during a `after each` hook we are skipping all of the remaining tests.
at (https://app3.syscloud.com/__cypress/runner/cypress_runner.js:151131:78)
at tryCatcher (https://app3.syscloud.com/__cypress/runner/cypress_runner.js:18744:23)
at (https://app3.syscloud.com/__cypress/runner/cypress_runner.js:13866:41)
at tryCatcher (https://app3.syscloud.com/__cypress/runner/cypress_runner.js:18744:23)
at Promise._settlePromiseFromHandler (https://app3.syscloud.com/__cypress/runner/cypress_runner.js:16679:31)
at Promise._settlePromise (https://app3.syscloud.com/__cypress/runner/cypress_runner.js:16736:18)
at Promise._settlePromise0 (https://app3.syscloud.com/__cypress/runner/cypress_runner.js:16781:10)
at Promise._settlePromises (https://app3.syscloud.com/__cypress/runner/cypress_runner.js:16857:18)
at _drainQueueStep (https://app3.syscloud.com/__cypress/runner/cypress_runner.js:13451:12)
at _drainQueue (https://app3.syscloud.com/__cypress/runner/cypress_runner.js:13444:9)
at ../../node_modules/bluebird/js/release/async.js.Async._drainQueues (https://app3.syscloud.com/__cypress/runner/cypress_runner.js:13460:5)
at Async.drainQueues (https://app3.syscloud.com/__cypress/runner/cypress_runner.js:13330:14)
From Your Spec Code:
at Context.P (webpack:///./node_modules/@currents/cypress-debugger-support/index.js:1:67245)
```
Before opening, please confirm:
Environment information
Describe the bug
When executing a spec which exceeds past 10-15 mins of runtime, the
cy.task('dumpEvents')
task is timing out on the default 60000ms task timeout. We increased the timeout to 300000ms (5 mins) and setfailedTestsOnly: true
parameter so only the failed test (which is only a couple mins long) will be stored but we are still getting the same issue.Expected behavior
The
cy.task('dumpEvents')
should not timeout for the failed test even if the complete spec file execution exceed 15 mins+ of runtime.Command and Setup
Full log and debug output