-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Investigate flaky addons/dlopen-ping-pong/test-worker #27186
Comments
@BethGriggs kicked off a stress run https://ci.nodejs.org/job/node-stress-single-test/18/nodes=aix61-ppc64/console but it failed with a different error while building the addons: 09:34:18 /home/iojs/build/workspace/node-stress-single-test/nodes/aix61-ppc64/tools/build-addons.js:58
09:34:18 main(process.argv[3]).catch((err) => setImmediate(() => { throw err; }));
09:34:18 ^
09:34:18
09:34:18 Error: Command failed: /home/iojs/build/workspace/node-stress-single-test/nodes/aix61-ppc64/out/Release/node /home/iojs/build/workspace/node-stress-single-test/nodes/aix61-ppc64/deps/npm/node_modules/node-gyp/bin/node-gyp.js rebuild --directory=/home/iojs/build/workspace/node-stress-single-test/nodes/aix61-ppc64/test/addons/async-hooks-id
09:34:18 g++: error: vfork: Resource temporarily unavailable
09:34:18 collect2: fatal error: gcc returned 1 exit status
09:34:18 compilation terminated.
09:34:18 gmake[1]: *** [Release/obj.target/binding.node] Error 1
09:34:18
09:34:18 at ChildProcess.exithandler (child_process.js:299:12)
09:34:18 at ChildProcess.emit (events.js:217:5)
09:34:18 at maybeClose (internal/child_process.js:1026:16)
09:34:18 at Socket.<anonymous> (internal/child_process.js:441:11)
09:34:18 at Socket.emit (events.js:217:5)
09:34:18 at Pipe.<anonymous> (net.js:662:12) {
09:34:18 killed: false,
09:34:18 code: 1,
09:34:18 signal: null,
09:34:18 cmd: '/home/iojs/build/workspace/node-stress-single-test/nodes/aix61-ppc64/out/Release/node /home/iojs/build/workspace/node-stress-single-test/nodes/aix61-ppc64/deps/npm/node_modules/node-gyp/bin/node-gyp.js rebuild --directory=/home/iojs/build/workspace/node-stress-single-test/nodes/aix61-ppc64/test/addons/async-hooks-id',
09:34:18 stdout: "gmake[1]: Entering directory `/home/iojs/build/workspace/node-stress-single-test/nodes/aix61-ppc64/test/addons/async-hooks-id/build'\n" +
09:34:18 ' CXX(target) Release/obj.target/binding/binding.o\n' +
09:34:18 ' SOLINK_MODULE(target) Release/obj.target/binding.node\n' +
09:34:18 "gmake[1]: Leaving directory `/home/iojs/build/workspace/node-stress-single-test/nodes/aix61-ppc64/test/addons/async-hooks-id/build'\n",
09:34:18 stderr: 'g++: error: vfork: Resource temporarily unavailable\n' +
09:34:18 'collect2: fatal error: gcc returned 1 exit status\n' +
09:34:18 'compilation terminated.\n' +
09:34:18 'gmake[1]: *** [Release/obj.target/binding.node] Error 1\n'
09:34:18 }
09:34:18 gmake: *** [test/addons/.buildstamp] Error 1 This new error looks like something we saw in the CITGM job (nodejs/build#1908 (comment)) where parallelism based on the number of CPU's (20 for our current AIX CI hosts) was causing resource issues. Line 12 in 73a244f
I've modified the stress job to export JOBS=5 on AIX (as we do in the https://ci.nodejs.org/job/node-test-commit-aix/ job) and rerun: https://ci.nodejs.org/job/node-stress-single-test/nodes=aix61-ppc64/20/
No failures in 100 runs. I don't think we've seen this fail recently, so maybe close and reopen if it reoccurs? There's some follow up work to set the cc FYI @nodejs/build @nodejs/platform-aix |
Sounds good to me. |
https://ci.nodejs.org/job/node-test-commit-aix/22493/nodes=aix61-ppc64/console
test-osuosl-aix61-ppc64_be-2
The text was updated successfully, but these errors were encountered: