Test suite fails
See original GitHub issueGreetings,
It looks like the automated tests fail when trying to hit the typedefsUrl.
⠧ Syncing type definitions in package.json...events.js:173
throw er; // Unhandled 'error' event
^
Error: incorrect header check
at Zlib.zlibOnError [as onerror] (zlib.js:162:17)
Emitted 'error' event at:
at errorOrDestroy (internal/streams/destroy.js:98:12)
at Gunzip.onerror (_stream_readable.js:717:7)
at Gunzip.emit (events.js:197:13)
at Zlib.zlibOnError [as onerror] (zlib.js:165:8)
error Command failed with exit code 1.
Simple reproduction case: Pull the repo; npm install; npm test
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Why test suites fail—and how to avoid breakdowns
One of the biggest causes of long-term test suite degradation arises when you constantly add on new tests every time development releases new...
Read more >Test suite failing when running all tests and tests passing ...
I am running a test suite with jest and puppeteer with 4 tests in it. When I run all of them 2 passes...
Read more >Solved: TestSuite Fails but all test cases are Passed
One of my TestSuite is showing FAILED (over all status in red at TestSuite level) but ALL Test Cases under this TestSuite are...
Read more >If the First Test Case Included in a Test Suite Fails, Can I ...
Since test cases within a test suite are sequential and have an execution order, Copado interprets that previous test success is required in ......
Read more >When tests fail (Libtool) - GNU.org
When the tests in the old test suite are run via make check , output is caught in per-test tests/ test-name .log files...
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 Free
Top 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
Sounds like a transient error with the type definitions source. Try again?
Edit: yeah it’s a type def source issue. Should probably be resolved soon. I’d imagine they are updating it or something.
Apparently unzipping is no longer needed. Shipped 0.6.1 to fix this.