-
Notifications
You must be signed in to change notification settings - Fork 110
Report timing out despite having __coverage__
#134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hmm, is the |
Yes, both frontend and backend. One coverage file is 2.4MB (out.json is 264KB). I do see now in testing the command |
Hmm, probably increasing task timeout to more than 1 minute should be enough. I will add it as an option to |
Actually, I will just increase the default timeout for that task to 3 minutes |
🎉 This issue has been resolved in version 1.12.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I configure the timeout configuration in cypress.json:
Still prompted this error:
There are the above problems when running on jenkins When I ran locally, I didn’t have this problem |
Hi,
For some reason, with
cypress run
orcypress open
can be set even when only visiting a page to ensure coverage on the server end), I'm getting the error:I'm getting the following debugging output before the error.
(Then the timeout occurs.)
I've added a mostly empty placeholder script file--with just a
console.log
statement even for those files which are only intended to be loaded to trigger server coverage, and I've confirmed that after instrumenting, this instrumented file is being loaded and that__coverage__
is set within it, but I'm still getting the above error.Is there anything else I should be looking for besides an absent
__coverage__
?The text was updated successfully, but these errors were encountered: