Deploys of my site fail on Netlify with the following output:
4:40:18 PM: error /opt/build/repo/node_modules/cypress: Command failed.
4:40:18 PM: Exit code: 1
4:40:18 PM: Command: node index.js --exec install
4:40:18 PM: Arguments:
4:40:18 PM: Directory: /opt/build/repo/node_modules/cypress
4:40:18 PM: Output:
4:40:18 PM: Installing Cypress (version: 4.5.0)
4:40:18 PM: [15:40:14] Downloading Cypress [started]
4:40:18 PM: [15:40:18] Downloading Cypress [failed]
4:40:18 PM: The Cypress App could not be downloaded.
4:40:18 PM: Does your workplace require a proxy to be used to access the Internet? If so, you must configure the HTTP_PROXY environment variable before downloading Cypress. Read more: https://on.cypress.io/proxy-configuration
4:40:18 PM: Otherwise, please check network connectivity and try again:
4:40:18 PM: ----------
4:40:18 PM: URL: https://download.cypress.io/desktop/4.5.0?platform=linux&arch=x64
4:40:18 PM: Error: Corrupted download
4:40:18 PM: Expected downloaded file to have checksum: 44470d2f42d6287eda84cc6441f4eb81c2f680c14afee83832a2facf23d9f384fd0e5a7f1a5bce9b72c5c6ace814eb9ec90fcd83682455ef89b808a377399ced
4:40:18 PM: Computed checksum: 19202e197566e5c624b4532944d0768d45442da252d76d622ee81cfc20d28e20850498ef9e159362cca1e807978441aa4e340488605390dc8139f64ede74101c
4:40:18 PM: Expected downloaded file to have size: 171297580
4:40:18 PM: Computed size: 171297580
4:40:18 PM: ----------
4:40:18 PM: Platform: linux (Ubuntu Linux - 16.04)
4:40:18 PM: Cypress Version: 4.5.0
Build passing with flying colours
Full error log: https://app.netlify.com/sites/herper-io/deploys/5ea99f9249d06e58a7bc6886
Github repository: https://github.com/jakeherp/portfolio/tree/master
Cypress: 4.5.0
Closing this, as I found that deleting and rebuilding the lock file has fixed this issue for me.
I found that going into Build & Deploy > Build Settings > Build and turning off "Activate Builds" and then deploying from the CLI fixes the issue. I wasn't in need of Cypress for deployment, so this worked for me. Might not be thing to do if you need to CI but for a quick deployment it works.
Most helpful comment
Closing this, as I found that deleting and rebuilding the lock file has fixed this issue for me.