Error checksum mismatch while updating
Something within This definitely seems node-gyp related, but I can't find anything where the maintainers of node-gyp have addressed it. stack at Block Stream._emit Chunk (/home/travis/.nvm/v0.10.26/lib/node_modules/npm/node_modules/block-stream/block-stream.js:2) gyp ERR! (/home/travis/.nvm/v0.10.26/lib/node_modules/npm/node_modules/tar/lib/parse.js:256:8) gyp ERR! Has anyone been able to find a related issue filed at node-gyp? The situation is a bit complicated for us now -- we ended up pinning Travis to test only Node v0.10.26 (instead of 0.10, which was trying to use the latest in that series, 0.10.41), and that solved our immediate issue with the checksum mismatch. stack at Block Stream.resume (/home/travis/.nvm/v0.10.26/lib/node_modules/npm/node_modules/block-stream/block-stream.js:) gyp ERR! Reader.resume (/home/travis/.nvm/v0.10.26/lib/node_modules/npm/node_modules/fstream/lib/reader.js:2) gyp ERR!
If a specific file was identified in the bug check message as being corrupted, you can try replacing that individual file manually.Here are a couple examples: gyp http GET gyp http 200 gyp WARN install got an error, rolling back install gyp ERR! not ok gyp http GET gyp http 200 gyp: /home/travis/.node-gyp/0.10.26/not found (cwd: /home/travis/build/adzerk/bifrost/node_modules/lru-native) while reading includes of gyp ERR! stack Error: `gyp` failed with exit code: 1 gyp ERR! This can also be caused by faulty hardware in the I/O path to the file (a disk error, faulty RAM, or a corrupted page file).To remedy this error, run the Emergency Recovery Disk (ERD) and allow the system to repair or replace the missing or damaged driver file on the system partition.If you are using Safe Mode to access a drive, use the Expand command to uncompress and copy the file to the target folder.
You can use the Expand command in the command line environment of Safe Mode.
If the file is used as part of the system startup process in Safe Mode, you need to start the computer using the Recovery Console in order to access the file.
If these methods fail, try reinstalling Windows and then restoring the system from a backup.
(nodejs/node-gyp#693) Anything changed in the travis environment that could be causing that? @Banzai Man I believe starting last wednesday afternoon (gmt 1), it started to slowly transition from working sometimes on previously-failing build to pretty much failing always.
not ok For some reason, node seems to receive corrupt files when downloading from a travis worker.
If you want to replace the file on a single-boot system with an NTFS partition, you need to restart the system, press F8 at the operating system Loader menu, and choose Safe Mode with Command Prompt.