Repository navigation
flaky: async-hooks.test-emit-after-on-destroyed #58199
Description
Test
async-hooks.test-emit-after-on-destroyed
Platform
Linux x64
Console output
---
duration_ms: 429.149
exitcode: 1
severity: fail
stack: |-
node:assert:95
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
null !== 1
at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux-containered/test/async-hooks/test-emit-after-on-destroyed.js:56:12)
at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux-containered/test/common/index.js:437:15)
at ChildProcess.emit (node:events:507:28)
at maybeClose (node:internal/child_process:1101:16)
at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: null,
expected: 1,
operator: 'strictEqual'
}
Node.js v25.0.0-pre
...Build links
Additional information
No response
Activity
RaisinTen commentedon May 27, 2025
Saw this happening on AIX - https://ci.nodejs.org/job/node-test-commit-aix/57444/nodes=aix72-ppc64/testReport/junit/(root)/async-hooks/test_emit_after_on_destroyed/
RaisinTen commentedon May 27, 2025
cc @nodejs/async_hooks
test: account for truthy signal in flaky async_hooks tests
test: account for truthy signal in flaky async_hooks tests
test: account for truthy signal in flaky async_hooks tests
RaisinTen commentedon Jun 3, 2025
I can confirm that #58478 has fixed this issue.
This flake was appearing in the reliability report 2-5 times daily from 2025-05-20 - nodejs/reliability#1206 till 2025-05-28 nodejs/reliability#1214. The PR landed on 2025-05-29 and then the flake went away in all recent reliability reports.
test: account for truthy signal in flaky async_hooks tests
test: account for truthy signal in flaky async_hooks tests
test: account for truthy signal in flaky async_hooks tests
test: account for truthy signal in flaky async_hooks tests