CI Reliability 2025-05-28

Failures in node-test-pull-request/67052 to node-test-pull-request/67154 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-05-28.md)

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

Progress

• Build timed out (after 30 minutes). Marking the build as failed. (5)
• Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 3306322, exit value: 1 (3)
• Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 3297692, exit value: 1 (2)
• ERROR: Error fetching remote repo 'origin' (2)
• fatal: No rebase in progress? (3)
• parallel/test-http2-debug (20)
• parallel/test-buffer-tostring-range (9)
• pummel/test-blob-slice-with-large-size (9)
• wpt/test-streams (5)
• parallel/test-stream-readable-to-web (4)
• sequential/test-performance-eventloopdelay (4)
• async-hooks/test-improper-unwind (3)
• parallel/test-runner-run-watch (3)
• parallel/test-zlib-brotli-16GB (3)
• sequential/test-tls-session-timeout (3)
• async-hooks/test-emit-after-on-destroyed (2)
• parallel/test-buffer-tostring-rangeerror (2)
• parallel/test-buffer-writefloat (2)
• parallel/test-buffer-zero-fill-reset (2)
• parallel/test-child-process-advanced-serialization-splitted-length-field (2)
• parallel/test-child-process-constructor (2)

Start with reports/2025-05-28.md and the linked node-test-pull-request jobs to inspect the failure details. Then investigate one listed failure, such as parallel/test-http2-debug, using the corresponding Node.js test entry point. Done means the selected failure is understood and its CI failure is resolved or appropriately tracked.