Inferred Node 6.9.1 consistently fails to install (Ubuntu 12.04)


#1

Sometimes one container, sometimes all 3.

circle.yml (Circle 1.0) - Just the relevant bits

machine:
  node:
    version: 6.9.1

The inferred step:

Downloading https://nodejs.org/dist/v6.9.1/node-v6.9.1-linux-x64.tar.xz...

######################################################################## 100.0%
Checksums do not match.
Binary download failed, trying source.

######################################################################## 100.0%
Checksums empty

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Binary download failed, trying source.
Detected that you have 32 CPU thread(s)
Set the number of jobs to 32 - 1 = 31 jobs to speed up the build
Installing node v1.0 and greater from source is not currently supported

nvm install 6.9.1 && nvm alias default 6.9.1 returned exit code 106

Action failed: set node.js version to 6.9.1

Some feature specs failing on 14.04 have kept us from bumping up at present, and we’re not ready to move this particular project to Circle 2.0 either (high complexity).


#2

I’m seeing this too, as well, on v6.2.1. Identical message except with 6.9.1 changed to 6.2.1.


#3

Our last successful build appears to have started ~2:27 PM Pacific Time.


#4

Same error, but for 6.10.2.

machine:
  node:
    version: 6

#5

#6

Please see the following from the NodeJS team: https://twitter.com/nodejs/status/849390481314373635


#7

Thanks for the updates @drazisil - will keep monitoring both threads.


#8

As an improvement to prevent this issue in the future…perhaps send the nodejs.org artifact requests through a caching proxy or similar, so that nodejs.org issues don’t impact builds? This could probably still be done if it’s an issue with the checksum list / mirror lists / etc.

Or is there another piece of the puzzle that prevents this? I would have guessed this was already being done for bandwidth conservation / faster downloads.


#9

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.