Repository navigation
Periodic failures with parallel/test-child-process-stdout-flush-exit #61393
Description
Activity
- changed the title
[-]Periodic[/-][+]Periodic failures with parallel/test-child-process-stdout-flush-exit[/+]on Jan 15, 2026 Hello, I see this at least on amd64 on Ubuntu 26.04 (20.19.4)
And I also have logs:
https://autopkgtest.ubuntu.com/results/autopkgtest-resolute/resolute/amd64/n/nodejs/20260115_194106_96c3b@/log.gzThis flaky issue was inadvertently fixed by PR #62020 (specifically commit
f951acf).The root cause was the explicit
process.exit(0)call. Under high load, when the stdout pipe buffer gets full,console.log('goodbye')becomes asynchronous. The immediateprocess.exit(0)forced the process to terminate before the event loop could flush the remaining buffer, cutting off the output.Since PR #62020 removed that unnecessary
process.exit(0), the process now naturally waits for the I/O event loop to drain, so this race condition will no longer occur. I believe this issue can be safely closed.This issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
Test
parallel/test-child-process-stdout-flush-exit
Platform
Linux ARM64
Console output
Build links
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.