Closed Bug 1205252 Opened 11 years ago Closed 10 years ago

Integration Trees closed for Taskcluster "npm" "install errors

Categories

(Taskcluster :: General, defect)

Product:
Taskcluster
Component:
General
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: cbook, Unassigned)

Details

affecting production trees now 11:32:41 INFO - npm WARN optional dep failed, continuing fsevents@0.3.8 11:33:07 INFO - npm ERR! Linux 3.13.0-48-generic 11:33:07 INFO - npm ERR! argv "node" "/usr/local/bin/npm" "install" 11:33:07 INFO - npm ERR! node v0.10.36 11:33:07 INFO - npm ERR! npm v2.14.3 11:33:07 INFO - npm ERR! shasum check failed for /tmp/npm-402-c363c4f3/registry.npmjs.org/glob/-/glob-3.2.3.tgz 11:33:07 INFO - npm ERR! Expected: e313eeb249c7affaa5c475286b0e115b59839467 11:33:07 INFO - npm ERR! Actual: da39a3ee5e6b4b0d3255bfef95601890afd80709 11:33:07 INFO - npm ERR! From: https://registry.npmjs.org/glob/-/glob-3.2.3.tgz 11:33:07 INFO - npm ERR! 11:33:07 INFO - npm ERR! If you need help, you may report this error at: 11:33:07 INFO - npm ERR! <https://github.com/npm/npm/issues> 11:33:12 INFO - npm ERR! Please include the following file with any support request: 11:33:12 INFO - npm ERR! /home/worker/gaia/npm-debug.log 11:33:12 INFO - make: *** [node_modules] Error 1
This appears to be a npm issue: https://github.com/npm/npm/issues/9600 https://github.com/npm/npm/issues/9601 Seeing this across trees and across docker images (tester and gaia-taskenv)
Flags: needinfo?(aus)
Huh, I thought we had our own node module cache? Why did we get rid of gaia_node_modules if this can happen?
We should be in the clear soon, assuming we don't have anything on our side caching the broken stuff: https://npmjs.statuspage.io/incidents/pyw00fmpjzrh
(In reply to Kevin Grandon :kgrandon from comment #3) > Huh, I thought we had our own node module cache? Why did we get rid of > gaia_node_modules if this can happen? I'm not sure, I thought taskcluster-npm-cache was supposed to correct this. maybe :aus has an idea about that.
(In reply to Kevin Grandon :kgrandon from comment #3) > Huh, I thought we had our own node module cache? Why did we get rid of > gaia_node_modules if this can happen? This can happen because of the in-tree modules which have their own requirements module wise. We could, as a hack, place those dependencies in gaia's main package.json file so that they would already be cached and would not have to be fetched when installing the in-tree modules. We did, however, put a lot of work into separating all the dependencies because it was a big mess. Ideally, we would be sub-caching all of the modules for the entire dependency tree with gaia's package.json as the root. The subsequent cache tarball would contain *ALL* of the things. There's some work involved there and it wouldn't be something I would have time for in the immediate. :gaye, any objections to rolling the in-tree module dependencies into gaia's package.json temporarly?
Flags: needinfo?(aus) → needinfo?(gaye)
Sounds like we should `npm shrinkwrap` and cache all of that?
(In reply to Aus Lacroix [:aus] from comment #6) > :gaye, any objections to rolling the in-tree module dependencies into gaia's > package.json temporarly? I am okay with this as long as we prioritize doing the cleaner thing afterwards.
Flags: needinfo?(gaye)
Oh yeah, we reopened an hour or two ago because the issue was resolved on npm's side. Leaving this open for figuring out if we need to do stuff on our side to prevent this in the future.
Is there any more work to do on this issue?
Flags: needinfo?(aus)
Severity: blocker → critical
There's no further work here. Our dependencies on npmjs.com are already pretty minimal. We only hit it once to cache things and that's it.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(aus)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.