Page MenuHomePhabricator

Update Fresh from Node.js 10 LTS to Node.js 12 LTS
Closed, ResolvedPublic

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Change 698271 had a related patch set uploaded (by Krinkle; author: Krinkle):

[fresh@master] fresh-node: Update to Debian 11 Bullseye and Node 12 LTS

https://gerrit.wikimedia.org/r/698271

It looks like Node 12 changed something that breaks compatibity with something related to how Qemu VMs manage their memory or their stdout buffer.

This is currently causing the containers to fail to run any node processes under Qemu.

Reported upstream: https://github.com/nodejs/node/issues/34709

The comments there suggest that it might have to do with an outdated Qemu. And indeed we use quite an old Qemu as well, the one on our CI agent is Qemu 2.8.1, from Debian 9 Stretch.

Debian 10 Buster offers Qemu 3.1 (https://packages.debian.org/buster/qemu).
Debian 11 Bullseye is currently in testing and would offer Qemu 5.2 (https://packages.debian.org/bullseye/qemu).

Krinkle triaged this task as High priority.

Change 721065 had a related patch set uploaded (by Hashar; author: Hashar):

[fresh@master] fresh-node: Update to Debian 11 Bullseye and Node 14 LTS

https://gerrit.wikimedia.org/r/721065

T267888 gives us a Node JS 14 based image (though with npm 6). https://gerrit.wikimedia.org/r/c/fresh/+/721065 is merely to try whether that get us past the Qemu related issue.

No luck with Node JS 14 either. https://github.com/nodejs/node/issues/19348 indicates it might be an issue in Qemu instructions translations. So anyway we need the qemu Jenkins agent to be updated to Bullseye and get a newer Qemu.

Change 698271 merged by jenkins-bot:

[fresh@master] Add fresh-node12 and fresh-node14, based on Debian 11 Bullseye

https://gerrit.wikimedia.org/r/698271

Krinkle moved this task from Inbox to Enhancement on the Fresh board.
Krinkle removed a project: Patch-For-Review.