Skip to content

Periodic failures with parallel/test-child-process-stdout-flush-exit #61393

@grahamc

Description

@grahamc

Test

parallel/test-child-process-stdout-flush-exit

Platform

Linux ARM64

Console output

2026-01-15T19:40:03.5158785Z     not ok 572 parallel/test-child-process-stdout-flush-exit
2026-01-15T19:40:03.5158846Z       ---
2026-01-15T19:40:03.5159008Z       duration_ms: 418.60800
2026-01-15T19:40:03.5159093Z       severity: fail
2026-01-15T19:40:03.5159158Z       exitcode: 1
2026-01-15T19:40:03.5159224Z       stack: |-
2026-01-15T19:40:03.5159287Z         node:assert:90
2026-01-15T19:40:03.5159370Z           throw new AssertionError(obj);
2026-01-15T19:40:03.5159426Z           ^
2026-01-15T19:40:03.5159799Z         
2026-01-15T19:40:03.5160025Z         AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
2026-01-15T19:40:03.5160103Z         + actual - expected
2026-01-15T19:40:03.5160161Z         
2026-01-15T19:40:03.5160227Z         + '\nfiller\n'
2026-01-15T19:40:03.5160288Z         - 'goodbye\n'
2026-01-15T19:40:03.5160616Z             at ChildProcess.<anonymous> (/build/node-v20.19.6/test/parallel/test-child-process-stdout-flush-exit.js:54:12)
2026-01-15T19:40:03.5160814Z             at ChildProcess.<anonymous> (/build/node-v20.19.6/test/common/index.js:474:15)
2026-01-15T19:40:03.5160926Z             at ChildProcess.emit (node:events:524:28)
2026-01-15T19:40:03.5161053Z             at maybeClose (node:internal/child_process:1104:16)
2026-01-15T19:40:03.5161228Z             at ChildProcess._handle.onexit (node:internal/child_process:304:5) {
2026-01-15T19:40:03.5161308Z           generatedMessage: true,
2026-01-15T19:40:03.5161380Z           code: 'ERR_ASSERTION',
2026-01-15T19:40:03.5161452Z           actual: '\nfiller\n',
2026-01-15T19:40:03.5161523Z           expected: 'goodbye\n',
2026-01-15T19:40:03.5161601Z           operator: 'strictEqual'
2026-01-15T19:40:03.5161658Z         }
2026-01-15T19:40:03.5161717Z         
2026-01-15T19:40:03.5161783Z         Node.js v20.19.6

Build links

  • (none public, sorry)

Additional information

I'm not sure if this is the right place to report this. However, we ran into this flaky test when building Node on a machine with a high core count and a lot of other compilation jobs happening.

Metadata

Metadata

Assignees

No one assigned

    Labels

    flaky-testIssues and PRs related to the tests with unstable failures on the CI.linuxIssues and PRs related to the Linux platform.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions