CI Reliability 2025-08-25

Failures in node-test-pull-request/68753 to node-test-pull-request/68852 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-25.md)

Open https://github.com/nodejs/reliability/blob/main/reports/2025-08-25.md to see failure details

Progress

• Build timed out (after 30 minutes). Marking the build as failed. (4)
• Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 1572969, exit value: 1 (2)
• Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 1574737, exit value: 1 (2)
• fatal error: ld terminated with signal 9 [Killed] (4)
• ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (3)
• parallel/test-max-old-space-size-percentage (13)
• parallel/test-fastutf8stream-flush-mocks (12)
• parallel/test-fastutf8stream-sync (12)
• parallel/test-inspector-network-fetch (8)
• parallel/test-http-keep-alive-empty-line (6)
• parallel/test-runner-mock-timers-scheduler (6)
• parallel/test-http-outgoing-end-cork (5)
• parallel/test-fs-write-stream-eagain (4)
• parallel/test-buffer-tostring-rangeerror (3)
• parallel/test-buffer-zero-fill-reset (3)
• parallel/test-child-process-advanced-serialization-splitted-length-field (3)
• parallel/test-http2-close-while-writing (3)
• parallel/test-without-async-context-frame (3)
• wpt/test-streams (3)
• async-hooks/test-improper-order (2)
• parallel/test-debugger-breakpoint-exists (2)
• parallel/test-repl-preview (2)
• parallel/test-runner-watch-mode-kill-signal (2)
• sequential/test-performance-eventloopdelay (2)
• sequential/test-single-executable-application (2)

Start by reading the linked CI jobs and the failure details in reports/2025-08-25.md, generated with ncu-ci walk pr --stats=true --markdown reports/2025-08-25.md. Investigate the listed build, process, linker, reporting, and Node.js test failures, then verify that the affected CI runs complete successfully without the repeated failures.