# Put output below this line
cypress-cloud run --spec cypress/e2e/test.spec.js --parallel --record --key xxxxxxxxxxxx --ci-build-id test-1
# Put output below this line
// eslint-disable-next-line no-undef
const { defineConfig } = require('cypress');
// eslint-disable-next-line no-undef
const { cloudPlugin } = require('cypress-cloud/plugin');
// eslint-disable-next-line no-undef
module.exports = defineConfig({
viewportWidth: 1500,
viewportHeight: 1200,
chromeWebSecurity: false,
watchForFileChanges: false,
redirectionLimit: 100,
defaultCommandTimeout: 60000,
pageLoadTimeout: 100000,
reporter: 'mochawesome',
reporterOptions: {
reportDir: 'cypress/reporters',
overwrite: true,
html: false,
js: true,
},
video: false,
e2e: {
setupNodeEvents(on, config) {
// eslint-disable-next-line no-undef
require('./cypress/plugins/index.js')(on, config);
return cloudPlugin(on, config);
},
specPattern: ['cypress/e2e/**/*.spec.js'],
},
});
Before opening, please confirm:
Environment information
Details
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: trueparameter 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
Details
Command (share the exact
cypressorcypress-cloudcommand you're running)Setup files cypress.config.j|ts|json
Full log and debug output
Details