-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
The Cypress App could not be unzipped #16631
Comments
We used to see this issue documented here: #3515 But haven't seen it in a while. |
Ran into this with |
hi @jennifer-shehane,
|
Not sure if this information is helpful or not, but I am running into this with a monorepo. I recently migrated several applications into a yarn workspace monorepo. Some of the applications have the same version of cypress, some have a different version. Error: ENOENT: no such file or directory, open '/root/.cache/Cypress/6.9.1/Cypress/resources/app/packages/server-ct/node_modules/lodash/_baseIsTypedArray.js'
Error: ENOENT: no such file or directory, open '/root/.cache/Cypress/7.7.0/Cypress/resources/app/packages/server/node_modules/yargs/locales/th.json'
Expected downloaded file to have checksum: 90012cdfc2823eba1921e9ed72e8e2156f409cbbc63d5918bf062b176f4f5e4467869cac609da02f75a229d402ee9acd52ea7fae8504c73196f2e98cbf002c6f Computed checksum: 38a7057a9e6edc43256e369e4115dd132c59e9d8ac4121a57763034e9414e7ea27f157f32722ce9ef70f54e082ea5b8e67731398280d15794d7a79adbca1d681
There are several more like the first one, just with different versions and/or different missing files. Individually/independently, before being combined into workspace / monorepo, these all worked. To me, not really knowing how yarn works and how the download / install works, but for the checksum it seems like a race condition where the zip file is either being created or removed while another install is trying to access it. I see it uses Maybe for the missing files maybe one install determines that the cache is there and tries to use it as another install is unzipping the cache (so the files are not all there yet and thus, depending on the exact timing, a different file is missing and causes the error) |
I was getting same issue: I've fixed like this:
I messed up a time with this issue, and I tried with permissions Hope this help anyone. |
any change? i got something like this
|
We're running into fails like the above poster's in our CI system:
It's proving very difficult to debug... The failure doesn't happen all the time but enough of the time to be frustrating. |
These are the hardest types of errors to find and fix! Your error is "Error: ENOENT: no such file or directory, open '/root/.cache/Cypress/11.1.0/Cypress/resources/app/node_modules/xml-parse-from-string/package.json'" which is not the same as the error in the original post, nor is it the same as the previous poster. Which CI provider are you using? |
i'm running into this also within a yarn workspaces monorepo. out of curiosity, why is there a label "needs reproduction"? Seems like previous posters have provided decent info. is there any more info/stack trace we can provide to help this along? |
Are you facing a hard error condition or an intermittent condition? Does this happen when you install manually locally or is it happening in a CI workflow? If yes, what is the name of the CI provider? Could you post your full |
@MikeMcC399 intermittent. it happens during CI often, i'd say daily but not the majority of the time. we typically restart the job and it'll succeed the following attempt. we're using Jenkins
|
Thank you very much for your logs! Comparing your report to the other reports, they are each failing at different points. There was an interesting insight in #16631 (comment) which suggested that there might be some cache overwriting causing the issue. That could explain why it is difficult to reproduce because it would depend on individual customer-specific workflows. I have never seen this issue in any of the example Cypress repositories. These are running typically with CircleCI and GitHub Actions as CI providers. Normally if the downloaded We had another issue where the Maybe somebody else has some other ideas about how to troubleshoot this issue? |
I did a quick check of installing wrong architectures on Ubuntu 22.04 and I did not get any unzip errors. Cypress just failed to verify. For instance I used the following to install a Windows zip on Ubuntu (don't try this at home 🙂 !) export CYPRESS_DOWNLOAD_PATH_TEMPLATE=https://download.cypress.io/desktop/12.17.3/win32-x64/cypress.zip
npm install cypress@12.17.3 -D -E --foreground-scripts Windows is different. If you try to install macOS on Windows, then you do get an unzip error. |
i was actually able to remedy our situation by making sure we "yarn cache clear" before "yarn install" during our CI thanks @MikeMcC399 for taking a look at all of this |
I am going to close this issue as resolved at this point. |
The text was updated successfully, but these errors were encountered: