-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
citgm-smoker fails on test-ibm-rhel7-s390x-2 with "not found: npm" with npm 7.4.2 #2525
Comments
FWIW with loglevel
whereas with nodejs/node@f8ab632 (commit before npm 7.4.2 update), https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2582/nodes=rhel7-s390x/consoleFull:
|
/cc @nodejs/npm as a heads up! |
Is |
A folder. |
FWIW I temporarily reenabled the host and kicked off a CI for nodejs/node#37018 (npm 7.4.3): https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2587/nodes=rhel7-s390x/console |
@richardlau we can try to book some time to pair on it next week if you're available 😊 |
Actually digging further it looks like
whereas it's a real directory on the other three LinuxONE hosts. I'm not sure why there's a discrepency (@AshCripps would you happen to know?). I saw there were some fixes in this area in npm 7.5.0 (nodejs/node#37117) so I started another
|
That is very odd - they should all be the same as I just ran the ansible scripts on them. It might be worth emailing them to get them to rebuild the machine/see if they can explain this? |
I'd like to hold off doing that right now as it looks like the current set up hits some sort of npm edge case (now we have identified an obvious difference between it and the other hosts). |
oooh that does rings a bell! I think we have some reports of installs in symlinked folders not working as expected and some fixes were shipped in |
👍. There's still some odd behaviour with npm 7.5.0 (citgm binaries appear to be put in the wrong place): #2525 (comment) |
This is an npm bug. Will be fixed in today's release. |
Also fixes up a few other places where we were checking isRoot and should have been checking isProjectRoot. Fix: nodejs/build#2525
Also fixes up a few other places where we were checking isRoot and should have been checking isProjectRoot. Fix: nodejs/build#2525 PR-URL: #217 Credit: @isaacs Close: #217 Reviewed-by: @nlf
https://ci.nodejs.org/job/citgm-smoker/2612/nodes=rhel7-s390x/ (Node.js master with npm 7.5.1) appears to be behaving as expected on |
Since the npm 7.4.2 update landed in Node.js (nodejs/node#36953) the
citgm-smoker
job has been failing ontest-ibm-rhel7-s390x-2
with error:The
citgm-smoker
job:smoker
directorynpm install --prefix=/home/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker --global --loglevel=error citgm
to install citgmcitgm-all -J
Further investigation shows that although the symlinks for npm are in
smoker/bin
the targets are not there:In fact the entire
npm
directory is missing fromsmoker/lib/node_modules
. A look at the logs suggests npm has unexpectedly removed a lot of packages at the install citgm step:e.g. https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2574/nodes=rhel7-s390x/console
Further investigation has revealed:
test-ibm-rhel7-s390x-2
. It doesn't occur ontest-ibm-rhel7-s390x-1
,test-ibm-rhel7-s390x-4
or any of the other platforms.test-ibm-rhel7-s390x-2
when building the commit (nodejs/node@f8ab632) immediately prior to the npm 7.4.2 update: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2582/nodes=rhel7-s390x/Only occurring on
test-ibm-rhel7-s390x-2
would suggest perhaps a machine specific issue but so far I've not been able to find an obvious difference between it and the other non-affected machines. As the problem only occurs on commits after the npm 7.4.2 update it could also be a regression in npm, but we're not seeing the problem elsewhere.I'm going to take
test-ibm-rhel7-s390x-2
offline temporarily.cc @nodejs/releasers @nodejs/npm
The text was updated successfully, but these errors were encountered: