Hi all,
We’ve been noticing pattern where updating NPM (via npm i -g npm@8
) fails on ppc64le. We’ve tested against Ubuntu Xenial and Bionic with no luck.
This issue is only occurs on ppc64le, Node.js 17.
The error snippet:
npm ERR! code ENETUNREACH
npm ERR! syscall connect
npm ERR! errno ENETUNREACH
npm ERR! request to https://registry.npmjs.org/npm failed, reason: connect ENETUNREACH 2606:4700::6810:1323:443
npm ERR! A complete log of this run can be found in:
npm ERR! /home/travis/.npm/_logs/2021-11-21T04_50_26_698Z-debug.log
For reference we’re keeping track of this issue on GitHub as well: Failing Node.js v17 NPM installations on ppc64le · Issue #3 · loopbackio/cicd · GitHub
After further investigation, this seems to be a more broad issue affecting any network traffic with Node.js v17 pcc64le:
https://app.travis-ci.com/github/achrinza/nodejs-ci-test/builds/243299904
Config:
# yaml-language-server: $schema=https://json.schemastore.org/travis.json
---
branches:
only:
- main
arch:
- arm64
- ppc64le
- s390x
os: linux
dist: bionic
language: node_js
node_js: [10, 12, 14, 16, 17]
env:
- NPM_MAJOR_VERSION=0
- NPM_MAJOR_VERSION=6
- NPM_MAJOR_VERSION=7
- NPM_MAJOR_VERSION=8
jobs:
exclude:
- node_js: 10
env: NPM_MAJOR_VERSION=8
before_install: |
if [ '0' != "$NPM_MAJOR_VERSION" ]
then
npm install --global npm@$NPM_MAJOR_VERSION
fi
script: npm test
With the build matrix above, NPM wasn’t able to contact the NPM registry for installing the project dependencies.