Error checksum mismatch while updating
I ended up updating node and npm (and a couple of other libraries we use) like so: install: # Install node via nvm at version defined in ARCH_NODE_VERSION - bin/run-integration source ~/.nvm/&& nvm install $ARCH_NODE_VERSION && nvm use $ARCH_NODE_VERSION - bin/run-integration npm install -g [email protected]$ARCH_NPM_VERSION # After updating npm it's saver to clean the cache - bin/run-integration npm cache clean - bin/run-integration npm install -g node-gyp-install - bin/run-integration node-gyp-install - bin/run-integration npm install --no-optional --no-progress version variable (in travis.yml) available even though language is not set to nodejs. command "node" "/home/travis/.nvm/v0.10.26/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /home/travis/build/adzerk/bifrost/node_modules/lru-native gyp ERR!
That would make choosing a different node version easier.) For some reason, node-gyp wasn't calculating the correct sha256sum of the downloaded it seems the file received was fine (at least the filesize was ok), so it doesn't seem to be a networking/proxy or caching issue.
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!
In this site you will be needed to enter your country, Ubuntu Release and check the packages sources, then click the Generate button at the end of the page to generate a file.
We figured this is a step in the right direction, since the production app is running in containers that have Node v0.10.26, so we should ensure that it builds specifically on that version. Abstract.error (/home/travis/.nvm/v0.10.26/lib/node_modules/npm/node_modules/fstream/lib/abstract.js:) gyp ERR! stack at Extract._stream End (/home/travis/.nvm/v0.10.26/lib/node_modules/npm/node_modules/tar/lib/extract.js:) gyp ERR! (/home/travis/.nvm/v0.10.26/lib/node_modules/npm/node_modules/tar/lib/parse.js:50:8) gyp ERR! the error basically means, that file got corrupted as it says. should then be able to copy over your modified files to the new checkout and use it.If you still get such crc errors and each time you redo the checkout which file it errors on is different, your hard drive is likely dying, or something else is corrupting it...I can try to reproduce this with a Joris: does the crash happen while you are synchronizing/running, or after a stop/start?If so, could you try running with -par=1 (to reduce risk for CPU problems, but I don't think that is the problem here, you'd get validation errors instead).