Cypress is stopped and json error is displayed on console
See original GitHub issueTest execution is stopped.
Current behavior:
Below error is displayed on command prompt.
{ Error: unexpected end of file
at Gunzip.zlibOnError (zlib.js:152:15)
errno: -5, code: 'Z_BUF_ERROR' }
Error: unexpected end of file
at Gunzip.zlibOnError (zlib.js:152:15)
cypress log:
Desired behavior:
Test should work.
Steps to reproduce:
Testing internal application
Versions
Latest
Issue Analytics
- State:
- Created 5 years ago
- Comments:21 (6 by maintainers)
Top Results From Across the Web
Error Messages | Cypress Documentation
This message means that Cypress was unable to find tests in the specified file. You'll likely get this message if you have an...
Read more >cypress-io/cypress - Gitter
Hey all, we have really flaky tests in CI and are trying to get console output to show in cypress logs but I...
Read more >Network Errors | Cypress examples (v9.2.0) - Gleb Bahmutov
Network Errors. # Error response from the server ... fetch all data from this REST json backend const root = 'https://jsonplaceholder.cypress.io' function ...
Read more >Cypress Uncaught Assertion Error despite cy ... - Stack Overflow
My guess is that cy.on('uncaught:exception', is not handling it because AssertionError is a different underlying type to Exception . You could raise this...
Read more >How to level-up your Cypress testing | Yost's Posts
When you run the Cypress test suite in headless mode, it's nice to be able to see console warnings and errors that may...
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 have discovered the root underlying cause of this and am working on a fix.
Released in
3.0.2
.