CI Reliability 2026-07-08

Failures in node-test-pull-request/74550 to node-test-pull-request/74638 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-07-08.md)

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

Progress

• test-runner/test-run-watch-cwd-isolation-none-argv (6)
• parallel/test-debugger-probe-failure-process-exit (5)
• sea/test-single-executable-application-empty (5)
• parallel/test-debugger-probe-max-hit-partial (3)
• sea/test-single-executable-application (3)
• parallel/test-debugger-probe-expression-throws (2)
• parallel/test-debugger-probe-script-throws (2)
• parallel/test-npm-install (2)
• test-runner/test-run-watch-emit-restarted (2)
• Command "git reset --hard" returned status code 128: (2)
• Failed to trigger fanned build (4)
• Failed to trigger node-test-commit (3)
• ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
• sh: line 12: [: -gt: unary operator expected (2)
• sh: line 1: 429:: command not found (2)

Start with reports/2026-07-08.md and the linked CI builds from node-test-pull-request/74550 through 74638. Review the listed failures, beginning with the repeated test-runner, debugger, sea, and npm-install cases, then trace each failure to its relevant test or CI step. Done means the recurring failures are diagnosed and the affected checks pass reliably.