Permafailing docker-image-updatebot rebuild on ESR102 due to old NPM version
Categories
(Firefox Build System :: Task Configuration, defect)
Tracking
(firefox-esr102 fixed)
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | fixed |
People
(Reporter: RyanVM, Assigned: RyanVM)
Details
Attachments
(1 file)
We pushed changes to ESR102 today that required a full rebuild of all the cached docker images for the repo. Unfortunately, the updatebot rebuild is busted:
https://firefoxci.taskcluster-artifacts.net/L-RoUb-AQTOfrjMX6DrKFg/1/public/logs/live_backing.log
npm ci
+ npm ci
[37;40mnpm[0m [0m[30;43mWARN[0m [0m[35mnpm[0m npm does not support Node.js v10.24.0
[0m[37;40mnpm[0m [0m[30;43mWARN[0m [0m[35mnpm[0m You should probably upgrade to a newer version of node as we
[0m[37;40mnpm[0m [0m[30;43mWARN[0m [0m[35mnpm[0m can't make any promises that npm will work with this version.
[0m[37;40mnpm[0m [0m[30;43mWARN[0m [0m[35mnpm[0m Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
[0m[37;40mnpm[0m [0m[30;43mWARN[0m [0m[35mnpm[0m You can find the latest version at https://nodejs.org/
[0m[?25l[[90m..................[0m] - : [32minfo[0m [35musing[0m node@v10.24.0[0m[K
We saw these failures before when we did credential rotation but ignored them because they weren't blocking anything anyway and we obviously don't care about running updatebot on that repo. Unfortunately, now we're in a position where every push wants to schedule this permafailing job because of the in-tree change we landed. We should probably just disable these jobs on the ESR tree.
|
Assignee | |
Comment 1•3 years ago
|
||
Removing the job looks good on Try.
https://treeherder.mozilla.org/jobs?repo=try&revision=20389b269868433fd3f22a1d71b4db2352b4053e
|
|
Assignee | |
Comment 2•3 years ago
|
||
|
||
Updated•3 years ago
|
|
|
Assignee | |
Comment 3•3 years ago
|
||
| uplift | ||
| Comment hidden (Intermittent Failures Robot) |
Description
•