Repository navigation
node-api/test_fatal/test_threads fails on arm in 14.x branch in debug mode #41208
Description
Version
14.18.3
Platform
arm
Subsystem
thread
What steps will reproduce the bug?
run test node-api/test_fatal/test_threads along with the test suite on the 14.x stream
How often does it reproduce? Is there a required condition?
100%
What is the expected behavior?
test to pass
What do you see instead?
16:09:19 not ok 3098 node-api/test_fatal/test_threads
16:09:19 ---
16:09:19 duration_ms: 0.715
16:09:19 severity: fail
16:09:19 exitcode: 1
16:09:19 stack: |-
16:09:19 assert.js:394
16:09:19 throw err;
16:09:19 ^
16:09:19
16:09:19 AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
16:09:19
16:09:19 assert.ok(p.status === 134 || p.signal === 'SIGABRT')
16:09:19
16:09:19 at Object. (/home/iojs/build/workspace/node-test-commit-arm-debug-mdawson/test/node-api/test_fatal/test_threads.js:20:8)
16:09:19 at Module._compile (internal/modules/cjs/loader.js:1085:14)
16:09:19 at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
16:09:19 at Module.load (internal/modules/cjs/loader.js:950:32)
16:09:19 at Function.Module._load (internal/modules/cjs/loader.js:790:12)
16:09:19 at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
16:09:19 at internal/main/run_main_module.js:17:47 {
16:09:19 generatedMessage: true,
16:09:19 code: 'ERR_ASSERTION',
16:09:19 actual: false,
16:09:19 expected: true,
16:09:19 operator: '=='
16:09:19 }
16:09:19 ...
Additional information
No response
Activity
mhdawson commentedon Dec 16, 2021
I found this while working on a debug job for ARM64 as I'd like to move over our debug testing to our arm machines. As part of a Red Hat team day looking at what we can do to move the ci closer to green, failures in the debug builds seem to be the top cause of failure. Looking at the logs it seems like it is because the debug builds require a lot of memory and the x86 container hosts don't have enough. Our ARM container hosts have a lot of memory (512G) so I'm hoping it would be a problem to run them there.
While creating the new job I came across what appears to be a persistent failure. Thinking we should mark as flaky so that we can move over.
mhdawson commentedon Dec 16, 2021
Only seems to affect the 14.x stream. Don't see it in the 12.x, 16.x, 17.x or main streams
targos commentedon May 3, 2023
Closing as v14.x is EoL.