You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Builds on the test CI are generally passing, which would point to a part of the build that is only run for the release tar balls (during or just before running tools/install.py).
Opening this here instead of the Build WG repository as no changes have been made to AIX release machine in the time period when the builds started to fail.
#62044 landed three days ago, and is both in the time period from when the build started failing (i.e. the nightly build prior to that passed and the subsequent ones are failing) and it modified the build to generate node.1 prior to running tools/install.py (and modified tools/install.py to install out/doc/node.1).
I tried to run the out/doc/node.1 target directly on the release machine, and it hangs up
bash-5.3$ gmake out/doc/node.1
npm warn cli npm v11.17.0 does not support Node.js v27.0.0-v8-canary2026062332a53c0490. This version of npm supports the following node versions: `^20.17.0 || >=22.9.0`. You can find the latest version at https://nodejs.org/.
added 369 packages, and audited 371 packages in 57s
142 packages are looking for funding
run `npm fund` for details
1 high severity vulnerability
To address all issues, run:
npm audit fix
Run `npm audit` for details.
|Hangup sudo -u iojs bash
bash-5.3#
Prior to #62044 we were not running any npm commands as part of the release AIX tarball builds.
Immediately no, as #62044 was reverted in #64091.
But based on #64090 (comment) I think there is still an issue in the Makefile on AIX for $(shell ...) commands if ksh (the default shell on AIX) is used instead of bash.
Activity
richardlau commentedon Jun 23, 2026
#62044 landed three days ago, and is both in the time period from when the build started failing (i.e. the nightly build prior to that passed and the subsequent ones are failing) and it modified the build to generate
node.1prior to runningtools/install.py(and modifiedtools/install.pyto installout/doc/node.1).I tried to run the
out/doc/node.1target directly on the release machine, and it hangs upPrior to #62044 we were not running any
npmcommands as part of the release AIX tarball builds.This might be #54590. I've added
to
/etc/sudoersand am running https://ci-release.nodejs.org/job/iojs+release/11883/nodes=aix72-power9/ to see if makes a difference.richardlau commentedon Jun 23, 2026
@aduh95 has pointed out an earlier error in the logs:
which would be in this target
node/Makefile
Lines 847 to 852 in 745a43e
and probably means an issue with the conditional, which prior to #62044 we would not have been running before.
miladfarca commentedon Jul 21, 2026
@sxa @richardlau is this still an issue?
richardlau commentedon Jul 21, 2026
Immediately no, as #62044 was reverted in #64091.
But based on #64090 (comment) I think there is still an issue in the Makefile on AIX for
$(shell ...)commands if ksh (the default shell on AIX) is used instead of bash.