test-crypto-secure-heap fails on IBM i

richardlau commented 3 years ago

Test: parallel/test-crypto-secure-heap
Platform: IBM i

Console Output:

09:04:30 not ok 525 parallel/test-crypto-secure-heap
09:04:30   ---
09:04:30   duration_ms: 3.340
09:04:30   severity: fail
09:04:30   exitcode: 1
09:04:30   stack: |-
09:04:30     node:assert:119
09:04:30       throw new AssertionError(obj);
09:04:30       ^
09:04:30     
09:04:30     AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
09:04:30     
09:04:30     null !== 0
09:04:30     
09:04:30         at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-ibmi/nodes/ibmi72-ppc64/test/parallel/test-crypto-secure-heap.js:59:10)
09:04:30         at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-ibmi/nodes/ibmi72-ppc64/test/common/index.js:377:15)
09:04:30         at ChildProcess.emit (node:events:379:20)
09:04:30         at Process.ChildProcess._handle.onexit (node:internal/child_process:285:12) {
09:04:30       generatedMessage: true,
09:04:30       code: 'ERR_ASSERTION',
09:04:30       actual: null,
09:04:30       expected: 0,
09:04:30       operator: 'strictEqual'
09:04:30     }
09:04:30   ...

Build Links: https://ci.nodejs.org/job/node-test-commit-ibmi/223

This test was newly added earlier in the week by 03c056401f23fe83ab6f16741759182e95a407bd and has been intermittently failing on IBM i (the CI for which is only run on the daily CI run) since.

richardlau commented 3 years ago

cc @nodejs/platform-ibmi

ThePrez commented 3 years ago

Can you please assign this to @dmabupt and me? This might be due to some differences in the openssl build between the IBM distribution and the CI, since the IBM distribution uses the system-provided openssl that may have IBM patches. I haven't done debug/investigation, just a hunch.

richardlau commented 3 years ago

Can you please assign this to @dmabupt and me?

I've assigned to you. I can't seem to assign to @dmabupt, probably because he's not in the nodejs org (that will happen as part of https://github.com/nodejs/node/issues/36569).

jasnell commented 3 years ago

Would be good to go ahead and open a PR marking it flaky on that platform (if you haven't done so already :-) ...)

targos commented 3 years ago

probably because he's not in the nodejs org

I think it's possible to assign external people after they commented on the thread.

richardlau commented 3 years ago

Would be good to go ahead and open a PR marking it flaky on that platform (if you haven't done so already :-) ...)

Opened https://github.com/nodejs/node/pull/36986.

nodejs / node

test-crypto-secure-heap fails on IBM i #36929