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
OK that's while building the tq-csa files so it's the point at which the system is pushed to the limit in terms of system use. It's possible we're over the limit now when JOBS=10 on a 16GB system (which is how that machine is configured). I've dropped it to JOBS=9 so hopefully that will resolve it.
Opening an issue to track this since it appears more complicated than we thought
From the logs I expect it's hitting an out of memory condition on that system which has 16GB RAM and is set to run with JOBS=10. I ran some tests in #4230 (comment) which suggested that JOBS=10 was ok but it's possible that it was close to the limit, particularly when building the tq-csa files which are very resource intensive to compile. It's also possible that the V8 update is resulting in it using more memory than it did during those compiles with 14.6.
What I'll try and do is run a couple of tests clearing the ccache and building the 14.6 and 15.2 builds
In the interim I've dropped that machine to JOBS=9 so that if we are just close to the limit that will hopefully help.
Hmmm seen again today with JOBS=9 durignt he test build of V5 15.6 on ibm-aix73-3. I don't see it always happening though (I've done some builds with an unpopulated ccache in the last week and haven't hit it).
Hard to say if this is purely down to increased RAM requirements of the later V8s or if there's another thing we need to address, but I never hit an issue on these machines when building from scratch without a populated ccache in the past when it would have needed to rebuild everything
Activity
sxa commentedon Oct 1, 2026
From the logs I expect it's hitting an out of memory condition on that system which has 16GB RAM and is set to run with
JOBS=10. I ran some tests in #4230 (comment) which suggested that JOBS=10 was ok but it's possible that it was close to the limit, particularly when building thetq-csafiles which are very resource intensive to compile. It's also possible that the V8 update is resulting in it using more memory than it did during those compiles with 14.6.What I'll try and do is run a couple of tests clearing the ccache and building the 14.6 and 15.2 builds
In the interim I've dropped that machine to
JOBS=9so that if we are just close to the limit that will hopefully help.sxa commentedon Oct 1, 2026
https://ci.nodejs.org/job/node-test-commit-aix/nodes=aix73-power9/65841 is running on the same machine and has just been chewing through the
tq-csafiles on the V8 15.2 branch and looks to have got through that phase without problems.sxa commentedon Oct 8, 2026
Hmmm seen again today with JOBS=9 durignt he test build of V5 15.6 on ibm-aix73-3. I don't see it always happening though (I've done some builds with an unpopulated ccache in the last week and haven't hit it).
sxa commentedon Oct 8, 2026
Ran through with
JOBS=8at https://ci.nodejs.org/job/node-test-commit-aix/nodes=aix73-power9/65966/consoleHard to say if this is purely down to increased RAM requirements of the later V8s or if there's another thing we need to address, but I never hit an issue on these machines when building from scratch without a populated ccache in the past when it would have needed to rebuild everything