no ARMv6 download of Nodejs 8.x available, 404 link #1382

jimmont · 2017-09-27T22:12:19Z

https://nodejs.org/en/download/current/:
ALL:
ALL:

see heading: "Linux Binaries (ARM)" with link "ARMv6" with href "https://nodejs.org/dist/v8.6.0/node-v8.6.0-linux-armv6l.tar.xz" which is a 404 error and browsing to "https://nodejs.org/dist/v8.6.0/" has no ARMv6 compatible download.

refack · 2017-09-28T01:08:45Z

@jimmont I think I found them nodejs/build#897 for some reason they were named ARM7, and it's actually the ARM7 binaries that are missing.

/cc @nodejs/build @nodejs/release

jimmont · 2017-09-28T01:28:05Z

@refack unfortunately the ARM7 binary you mentioned from https://nodejs.org/dist/v8.6.0/node-v8.6.0-linux-armv7l.tar.xz segfaults on my ARM6 machine so I don't think it's an option.

jimmont · 2017-09-28T01:31:57Z

Reverting to Nodejs 8.4 per what appears to be the best option based on descriptions of the most recent 2 security issues (as of today).
https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/
https://groups.google.com/forum/#!forum/nodejs-sec

refack · 2017-09-28T01:32:17Z

So it's not a simple misnaming, shame.
You might want to checkout nodesource's repository https://github.com/nodesource/distributions, they build binaries to various linux distributions and support ARM6 & ARM7

jimmont · 2017-09-28T01:41:41Z

Unfortunately Nodejs 8.x and 7.x are not supported for ARM6 on nodesource. Appreciate the tip @refack, might be time to retire the rpi I've been using.

joaocgreis · 2017-09-28T02:21:31Z

This happened because all of our ARMv6 infra is down. ARMv6 is still supported and the binary will probably be released as soon as we're able to get the machines back online (cc @rvagg).

The ARMv7 issue is a different one, ref nodejs/build#829.

mhdawson · 2017-09-28T13:46:59Z

I guess I need to find time to get the backup Raspberry PI 1 (ARM v6) connected to the CI. However, that won't like be until at least after Node Interactive.

jimmont · 2017-10-02T20:40:00Z

@mhdawson Michael is it possible to please update the page to reflect the status for these downloads accurately? If there's a change in support or outage (indicated above) it would be helpful to have that information on the website so that we can plan accordingly. Thank you.

refack · 2017-10-02T21:27:00Z

ping @jasnell who cut the release (No ARM6 and ARM7 are corrupt)

johnwebbcole · 2017-10-03T23:58:32Z

I appears that node source isn't an option for armv6l versions of v8.x

## Installing the NodeSource Node.js v8.x repo...


## You appear to be running on ARMv6 hardware. Unfortunately this is not currently supported by the NodeSource Linux distributions. Please use the 'linux-armv6l' binary tarballs available directly from nodejs.org for Node.js v4 and later.

Any word on the armv6 builds?

Thx!

mhdawson · 2017-10-11T16:05:31Z

The arm machine seems to be online but fails with this:

/home/iojs/build/ws/out/Release/.deps//home/iojs/build/ws/out/Release/obj.target/v8_base/deps/v8/src/ic/arm/handler-compiler-arm.o.d.raw   -c -o /home/iojs/build/ws/out/Release/obj.target/v8_base/deps/v8/src/ic/arm/handler-compiler-arm.o ../deps/v8/src/ic/arm/handler-compiler-arm.cc
FATAL: command execution failed
java.nio.channels.ClosedChannelException
	at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208)
	at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222)
	at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)
	at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287)
	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181)
	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283)
	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503)
	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248)
	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200)
	at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFil

@rvagg is it possible that some cleanup is needed on the release machine ?

bertlea · 2017-11-24T01:51:29Z

Hi Guys, the same issue seems happening to v8.9.1 now. No armv6l distribution in the download list. the v8.9.0 still got it and also v9.2.0 got it too.

mhdawson · 2017-11-24T14:27:11Z

We do have issues with our arm6 builds in that they take a long time to compile due to the low machine resources and often timeout or have some other issue during the long run.

@gibfahn I've added a new arm6 only build that we can run to rebuild just the arm6 binaries in case of failure. If we run that for 8.9.1 with the right parameters is that enough or do we need additional steps to sign/validate the hashes ?

gibfahn · 2017-11-25T11:22:02Z

If we run that for 8.9.1 with the right parameters is that enough or do we need additional steps to sign/validate the hashes ?

Steps are:

Run the job with the correct parameters
I run tools/release.sh 8.9.1 to sign the shasums txt
Run rm locale/en/blog/release/v8.9.1.md && scripts/release-post.js 8.9.1 and submit a PR.

Only the second needs to be done by me.

mhdawson · 2017-11-28T15:07:47Z

@gibfahn what I'm trying to figure out would be the flow if we wanted to publish an arm binary after the fact to see if it is feasible. We could start but running the arm6 only job with the same date/commit hash.

We now have a binary and a new hash. Would rerunning tools/release.sh do the right thing an result with a file that had the old hashes as well as the new one ?

gibfahn · 2017-11-28T16:26:48Z

We now have a binary and a new hash. Would rerunning tools/release.sh do the right thing an result with a file that had the old hashes as well as the new one ?

Yes, I just ran tools/release.sh -s v8.9.1 and it created a new hash.

You have to open a new PR against nodejs.org though, see #1489

mhdawson · 2017-11-28T16:50:51Z

We must be missing a step as https://nodejs.org/dist/v8.9.1/node-v8.9.1-linux-armv6l.tar.xz still shows as 404. Maybe there is a step to push the binary into dist ?

gibfahn · 2017-11-28T19:05:40Z

▶▶▶ tools/release.sh                                                                                                                                                      ~/wrk/com/DANGER/node (master*)
# Selecting GPG key ...
You have multiple GPG keys:

/Users/gib/.gnupg/pubring.gpg
-----------------------------
sec   rsa4096 2016-10-07 [SC]
      77984A986EBC2AA786BC0F66B01FBB92821C587A
uid           [ultimate] Gibson Fahnestock <[email protected]>
ssb   rsa4096 2016-10-07 [E]

1) 821C587A
2) 2C482931
Select a key: 2

Using GPG key: 2C482931
  Fingerprint: 77984A986EBC2AA786BC0F66B01FBB92821C587A

# Checking for releases ...
No releases to promote!

The script should do that, not sure why it doesn't.

mhdawson · 2017-11-29T14:56:05Z

@gibfahn are the manual steps for the promotion something we can do by hand. I see you landed the update to node.js org but we still need to fix the 404 on the download.

gibfahn · 2017-11-29T15:24:56Z

@mhdawson yes, that's what I tried to do by running tools/release.sh, but it didn't find any builds to promote.

Docs for that are here: https://github.com/nodejs/node/blob/master/doc/releases.md#12-promote-and-sign-the-release-builds

mhdawson · 2017-11-30T23:22:47Z

Ok just checked an job to build the 8.9.1 binaries for arm6 passed here: https://ci-release.nodejs.org/job/iojs+release-arm6-only/nodes=pi1-raspbian-wheezy/

@gibfahn can you re-run the script to promote ?

gibfahn · 2017-12-01T09:21:36Z

Done

Refs: nodejs#1382 (comment)

Refs: #1382 (comment)

mhdawson · 2017-12-01T21:44:11Z

@gibfahn thanks, download link now works. I think we also have the process for recovering if we don't get an arm build out. Where do you think we should best document that ? The Release repo ?

gibfahn · 2017-12-02T11:02:59Z

Where do you think we should best document that ? The Release repo ?

I think it should go in the release guide:

https://github.com/nodejs/node/blob/master/doc/releases.md#12-promote-and-sign-the-release-builds

bertlea · 2017-12-02T11:05:10Z

Thank you all for fixing that. Will download and install that to my Raspberry Pi Zero W on Monday. @jimmont , I guess you wanted to changed the title to "... 8.x..." instead of "...8.6.x...".

jimmont · 2017-12-02T16:40:37Z

@bertlea yes thanks.

mhdawson · 2017-12-04T15:29:25Z

PR for addition to docs: nodejs/node#17455

fhemberger · 2017-12-19T08:52:37Z

Closing, as the link works now.

refack mentioned this issue Sep 28, 2017

Arm v7 builds are reported as arm v6 nodejs/build#897

Closed

fhemberger added the external/build label Oct 11, 2017

gibfahn added a commit to gibfahn/nodejs.org that referenced this issue Dec 1, 2017

v8.9.1: add arm (second try) and revert 8.9.1 date

be6f3ac

Refs: nodejs#1382 (comment)

gibfahn mentioned this issue Dec 1, 2017

v8.9.1: add arm (second try) and revert 8.9.1 date #1493

Merged

MylesBorins pushed a commit that referenced this issue Dec 1, 2017

v8.9.1: add arm (second try) and revert 8.9.1 date

df4ca06

Refs: #1382 (comment)

jimmont changed the title ~~no ARMv6 download of Nodejs 8.6.0 available, 404 link~~ no ARMv6 download of Nodejs 8.6.x available, 404 link Dec 2, 2017

jimmont changed the title ~~no ARMv6 download of Nodejs 8.6.x available, 404 link~~ no ARMv6 download of Nodejs 8.x available, 404 link Dec 2, 2017

richardlau mentioned this issue Dec 4, 2017

doc: add info on post-publishing ARM6 builds nodejs/node#17455

Closed

3 tasks

fhemberger closed this as completed Dec 19, 2017

Uh oh!

no ARMv6 download of Nodejs 8.x available, 404 link #1382

no ARMv6 download of Nodejs 8.x available, 404 link #1382

Comments

jimmont commented Sep 27, 2017

refack commented Sep 28, 2017

Uh oh!

jimmont commented Sep 28, 2017

Uh oh!

jimmont commented Sep 28, 2017

Uh oh!

refack commented Sep 28, 2017

Uh oh!

jimmont commented Sep 28, 2017

Uh oh!

joaocgreis commented Sep 28, 2017

Uh oh!

mhdawson commented Sep 28, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jimmont commented Oct 2, 2017

Uh oh!

refack commented Oct 2, 2017

Uh oh!

johnwebbcole commented Oct 3, 2017

Uh oh!

mhdawson commented Oct 11, 2017

Uh oh!

bertlea commented Nov 24, 2017

Uh oh!

mhdawson commented Nov 24, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gibfahn commented Nov 25, 2017

Uh oh!

mhdawson commented Nov 28, 2017

Uh oh!

gibfahn commented Nov 28, 2017

Uh oh!

mhdawson commented Nov 28, 2017

Uh oh!

gibfahn commented Nov 28, 2017

Uh oh!

mhdawson commented Nov 29, 2017

Uh oh!

gibfahn commented Nov 29, 2017

Uh oh!

mhdawson commented Nov 30, 2017

Uh oh!

gibfahn commented Dec 1, 2017

Uh oh!

mhdawson commented Dec 1, 2017

Uh oh!

gibfahn commented Dec 2, 2017

Uh oh!

bertlea commented Dec 2, 2017

Uh oh!

jimmont commented Dec 2, 2017

Uh oh!

mhdawson commented Dec 4, 2017

Uh oh!

fhemberger commented Dec 19, 2017

Uh oh!

mhdawson commented Sep 28, 2017 •

edited

Loading

mhdawson commented Nov 24, 2017 •

edited

Loading