Repository navigation
node-daily-v18.x-staging builds fail on rhel8-s390x since 1 Nov #3950
Description
Starting on 1 Nov, node-daily-v18.x-staging builds have been consistently failing on rhel8-s390x.
e.g.
- 31 Oct (passed): https://ci.nodejs.org/view/Node.js%20Daily/job/node-daily-v18.x-staging/362/
- 1 Nov (failed): https://ci.nodejs.org/view/Node.js%20Daily/job/node-daily-v18.x-staging/363/
From https://ci.nodejs.org/job/node-test-commit-linuxone/46599/nodes=rhel8-s390x/console
09:06:28 npm warn cli npm v10.7.0 does not support Node.js v18.20.5-pre. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
09:10:05 npm error Exit handler never called!
09:10:05 npm error This is an error with npm itself. Please report this error at:
09:10:05 npm error <https://github.com/npm/cli/issues>
09:10:05
09:10:05
09:10:05 npm error A complete log of this run can be found in: /home/iojs/build/workspace/citgm-smoker/npm_cache/_logs/2024-11-01T09_06_28_772Z-debug-0.log
09:10:05 make[1]: *** [Makefile:754: tools/doc/node_modules] Error 1
09:10:05 make: *** [Makefile:583: run-ci] Error 2The warning can be ignored (expected for non-releases). I'm slightly concerned that the log references a path in the citgm-smoker workspace (from a node-test-commit-linuxone job!).
Both of the above builds ran on commit nodejs/node@1c4decc so we can rule out any of the subsequent changes landed on v18.x-staging. Since it doesn't appear at first to be due to a code change (and other platforms haven't failed), I'm opening for investigation here in nodejs/build.
Activity
richardlau commentedon Nov 5, 2024
Note to check whether this only affects test-ibm-rhel8-s390x-4 (all four failing daily v18.x-staging builds all ran on that machine).
This includes, so far, rhel9-s390x.
richardlau commentedon Nov 5, 2024
Resumed CI for nodejs/node#55708 (was failing on test-ibm-rhel8-s390x-4 with the same error) -- https://ci.nodejs.org/job/node-test-commit-linuxone/46644/nodes=rhel8-s390x/ is running on test-ibm-rhel8-s390x-1
aduh95 commentedon Nov 5, 2024
FWIW I tried cherry-picking all the npm updates to see if that would improve the outcome, but no, it fails with the same error
richardlau commentedon Nov 5, 2024
https://ci.nodejs.org/job/node-test-commit-linuxone/46648/nodes=rhel8-s390x/console
So from the log it looks like npm failed to reach the registry. The fetch error on the audits endpoint would indicate that it's trying (and failing) IPv6. Node.js 18 doesn't have happy eyeballs, which would probably explain why the other release lines haven't been affected on this machine.
richardlau commentedon Nov 6, 2024
I've opened #3952, which has been deployed on to three of the four rhel8-s390x test machines (I'll update the last one when the citgm job it is currently running completes).
richardlau commentedon Nov 12, 2024
Well annoyingly rhel9-s390x is now failing, after I started leave 😞.
ansible: add getaddrinfo config to prefer IPv4 (nodejs#3952)