CI Reliability 2026-05-06

Failures in node-test-pull-request/73090 to node-test-pull-request/73188 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-06.md)

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

Progress

• Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): Failed to exec spawn helper: pid: 3278933, exit code: 1, error: 0 (none) (2)
• Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): Failed to exec spawn helper: pid: 3280872, exit code: 1, error: 0 (none) (2)
• Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 818939, exit value: 1 (2)
• fatal: No rebase in progress? (3)
• parallel/test-sqlite-database-sync (6)
• parallel/test-process-finalization (4)
• sequential/test-gc-http-client-onerror (3)
• sequential/test-perf-hooks (3)
• sequential/test-watch-mode-worker (3)
• test-runner/test-run-watch-dependency-repeatedly (2)
• test-runner/test-run-watch-emit-restarted (2)

Start with reports/2026-05-06.md linked from the issue and the ncu-ci walk command output. Review the listed Jenkins failures, then run the named Node.js tests, including parallel/test-sqlite-database-sync and the test-runner watch tests, to distinguish reproducible failures from infrastructure errors. Done means the tracked failures are explained and the CI jobs return green.