Repository navigation
AIX: Test failures - malloc(0) #7549
Copy link
Copy link
Closed
Labels
clusterIssues and PRs related to the cluster subsystem.Issues and PRs related to the cluster subsystem.cryptoIssues and PRs related to the crypto subsystem.Issues and PRs related to the crypto subsystem.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Description
Activity
- addedcryptoIssues and PRs related to the crypto subsystem.Issues and PRs related to the crypto subsystem.clusterIssues and PRs related to the cluster subsystem.Issues and PRs related to the cluster subsystem.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
on Jul 5, 2016 Build to see if fix from 7229 resolves all 4 issues or only the 3 seen previously:
- changed the title
[-]AIX: Test failures - new ?[/-][+]AIX: Test failures - malloc(0)[/+]on Jul 6, 2016 From the previous run, seems to only resolve the 3 seen previously so the 4th is a new issue. Opened new issue here: #7563
What was done in V8 inspector is removing
<vector>from theinspector-agent.hheader. This way STL did not leak to env.h and the rest of the node.I do not think any tests instantiate the Inspector for now ('--inspect' needs to be passed to start the inspector) so I do not know if Inspector can be triggering this...
@mhdawson is there anything left to do here?
There is, it's on my plate.
Reacted by Colin IhrigSee discussion here: #7564
- added 2 commits that reference this issue
on Sep 9, 2016 - added a commit that references this issue
on Nov 22, 2016 - added a commit that references this issue
on Nov 22, 2016 - added a commit that references this issue
on Jul 27, 2026
Metadata
Metadata
Assignees
Labels
clusterIssues and PRs related to the cluster subsystem.Issues and PRs related to the cluster subsystem.cryptoIssues and PRs related to the crypto subsystem.Issues and PRs related to the crypto subsystem.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Now that AIX is building again after recent build breaks there are 4 failing tests:
https://ci.nodejs.org/job/node-test-commit-aix/nodes=aix61-ppc64/244/
Some of them look potentially related to: #7229.
Will need to investigate to see if its new or a regression.
not ok 6 parallel/test-async-wrap-post-did-throw # FATAL ERROR: node::RandomBytesRequest() Out of Memory --- duration_ms: 0.423 ... not ok 8 parallel/test-async-wrap-throw-from-callback # # assert.js:89 # throw new assert.AssertionError({ # ^ # AssertionError: pre closed with code null # at ChildProcess.child.on (/home/iojs/build/workspace/node-test-commit-aix/nodes/aix61-ppc64/test/parallel/test-async-wrap-throw-from-callback.js:70:14) # at emitTwo (events.js:106:13) # at ChildProcess.emit (events.js:191:7) # at maybeClose (internal/child_process.js:852:16) # at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5) --- duration_ms: 1.36 ... not ok 104 parallel/test-cluster-disconnect-handles # Debugger listening on [::1]:12346 # # /home/iojs/build/workspace/node-test-commit-aix/nodes/aix61-ppc64/test/parallel/test-cluster-disconnect-handles.js:86 # throw ex; # ^ # AssertionError: worker did not exit normally # at Worker.worker.once.common.mustCall (/home/iojs/build/workspace/node-test-commit-aix/nodes/aix61-ppc64/test/parallel/test-cluster-disconnect-handles.js:32:12) # at Worker. (/home/iojs/build/workspace/node-test-commit-aix/nodes/aix61-ppc64/test/common.js:407:15) # at Worker.g (events.js:286:16) # at emitTwo (events.js:111:20) # at Worker.emit (events.js:191:7) # at ChildProcess. (cluster.js:380:14) # at ChildProcess.g (events.js:286:16) # at emitTwo (events.js:106:13) # at ChildProcess.emit (events.js:191:7) # at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12) --- duration_ms: 0.943 ... not ok 179 parallel/test-crypto-random # FATAL ERROR: node::RandomBytesRequest() Out of Memory --- duration_ms: 0.367 ...