Closed Bug 1431377 Opened 8 years ago Closed 7 years ago

Intermittent failure 'Error 418 I am a teapot' while running 'npm install -g jsdoc@3.5.5' when docker image for linting gets built

Categories

(Taskcluster Graveyard :: Docker Images, defect)

Product:
Taskcluster Graveyard
Component:
Docker Images
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: aryx, Unassigned)

Details

(Keywords: intermittent-failure)

https://treeherder.mozilla.org/logviewer.html#?job_id=157104658&repo=mozilla-inbound npm install -g jsdoc@3.5.5 npm ERR! registry error parsing json npm ERR! Linux 4.4.0-98-generic npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "jsdoc@3.5.5" npm ERR! node v6.9.1 npm ERR! npm v3.10.8 npm ERR! Unexpected token < in JSON at position 1 npm ERR! npm ERR! <?xml version="1.0" encoding="utf-8"?> npm ERR! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" npm ERR! "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> npm ERR! <html> npm ERR! <head> npm ERR! <title>418 I am a teapot</title> npm ERR! </head> npm ERR! <body> npm ERR! <h1>Error 418 I am a teapot</h1> npm ERR! <p>I am a teapot</p> npm ERR! <h3>Guru Mediation:</h3> npm ERR! <p>Details: cache-sjc3633-SJC 1516270785 1526261191</p> npm ERR! <hr> npm ERR! <p>Varnish cache server</p> npm ERR! </body> npm ERR! </html> npm ERR! npm ERR! npm ERR! If you need help, you may report this error at: npm ERR! <https://github.com/npm/npm/issues> npm ERR! Please include the following file with any support request: npm ERR! /build/npm-debug.log The command [/bin/sh -c bash /tmp/system-setup.sh] returned a non-zero code: 1
Component: General → Docker Images
Product: Release Engineering → Taskcluster
This sounds like a pretty typical failure of the npm mirrors -- that's an external service. We already minimize the use of external services like npm by only referencing them from image build tasks, so I don't think there's much more we can do here in a practical sense. Running our own full npm mirror would be hard and probably wouldn't help (presumably we'd run the same teapot-prone software they run). I think we may just need to re-trigger these jobs as they come up or, if it becomes more frequent, wrap the `npm` command to do some kind of exponential-backoff retry.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Product: Taskcluster → Taskcluster Graveyard
You need to log in before you can comment on or make changes to this bug.