cypress: Unzipping Cypress fails on Concourse
Current behavior:
Unzipping Cypress fails on concourse with an error from the unzipping tool used by Cypress, yauzl:
error /tmp/build/ec0e34e0/src/node_modules/cypress: Command failed.
Exit code: 1
Command: node index.js --exec install
Arguments:
Directory: /tmp/build/ec0e34e0/src/node_modules/cypress
Output:
Installing Cypress (version: 3.1.0)
25l[16:53:03] Downloading Cypress [started]
[16:53:03] Downloading Cypress 0% 0s [title changed]
[16:53:03] Downloading Cypress 22% 1s [title changed]
[16:53:04] Downloading Cypress 95% 0s [title changed]
[16:53:04] Downloaded Cypress [title changed]
[16:53:04] Downloaded Cypress [completed]
[16:53:04] Unzipping Cypress [started]
25hevents.js:183
throw er; // Unhandled 'error' event
^
Error: invalid central directory file header signature: 0x1e02014b
at /tmp/build/ec0e34e0/src/node_modules/yauzl/index.js:249:70
at /tmp/build/ec0e34e0/src/node_modules/yauzl/index.js:618:5
at /tmp/build/ec0e34e0/src/node_modules/fd-slicer/index.js:32:7
at FSReqWrap.wrapper [as oncomplete] (fs.js:658:17)
There also seems to be a previous error when trying to run cypress, not sure if they are related.
Desired behavior:
Downloading and running of Cypress successful on Concourse
Steps to reproduce: (app code and test code)
Install Cypress on Concourse
Versions
Cypress 3.1.5 Yarn 1.9.4 Node 8.12.0
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 8
- Comments: 35 (10 by maintainers)
Commits related to this issue
- chore(npm): Try regenerating yarn.lock to fix cypress error? @see https://github.com/cypress-io/cypress/issues/3515 Signed-off-by: Jesse Stuart <hi@jessestuart.com> — committed to jessestuart/jesses.io by jessestuart 5 years ago
- chore(npm): Try regenerating yarn.lock to fix cypress error? @see https://github.com/cypress-io/cypress/issues/3515 Signed-off-by: Jesse Stuart <hi@jessestuart.com> — committed to jessestuart/jesses.io by jessestuart 5 years ago
- chore(npm): Try regenerating yarn.lock to fix cypress error? @see https://github.com/cypress-io/cypress/issues/3515 Signed-off-by: Jesse Stuart <hi@jessestuart.com> — committed to jessestuart/jesses.io by jessestuart 5 years ago
- chore(npm): Try regenerating yarn.lock to fix cypress error? @see https://github.com/cypress-io/cypress/issues/3515 Signed-off-by: Jesse Stuart <hi@jessestuart.com> — committed to jessestuart/jesses.io by jessestuart 5 years ago
Any update on what the timeline for https://github.com/cypress-io/cypress/pull/4193 being merged might be? This is still causing quite a bit of pain for my team!
Released in
3.4.0.we need to include zip size and checksums for the downloaded zip file for each platform when we build them. The NPM CLI should check these after downloading …
On Fri, Apr 5, 2019 at 10:17 AM Matthías Leó notifications@github.com wrote:
– Dr. Gleb Bahmutov, PhD
Schedule video chat / phone call / meeting with me via https://calendly.com/bahmutov gleb.bahmutov@gmail.com @bahmutov https://twitter.com/@bahmutov https://glebbahmutov.com/ https://glebbahmutov.com/blog https://github.com/bahmutov
I’m running into the same issue on BuildKite and when trying to install on Debian. Only happening with 3.1.5. Previous version I used (3.1.3) installs without issue. Ran
rm -rf node_modules && yarn installand this did not fix the issue for me.Issue seems to be the same as what ruffle1986 mentions.
Main issue is:
The Cypress App could not be unzipped.Error: end of central directory record signature not foundFull output:
Seems to be an issue with version 3.1.5 (for me), I downgraded to 3.1.0 and it worked.
I’m experiencing the same on Travis. This issue is kind of duplication of mine: #3439
Now I see that the title of my issue is not appropriate. The memory leak message is just a warning. The problem is that when the
yauzlmodule does the unizpping, it fails.We may also want to look into implementing better error handling instead of crashing for yauzl as described here: https://github.com/thejoshwolfe/yauzl#how-to-avoid-crashing
@aryzing rerunning
yarn installwill recreateyarn.lock, but I get it. Sometimes these things don’t end up pulling the same package versions that once worked.