CI Reliability 2026-07-12

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

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

Progress

• Build timed out (after 60 minutes). Marking the build as failed. (2)
• ERROR: Error fetching remote repo 'origin' (3)
• Command "git reset --hard" returned status code 128: (2)
• fatal: No rebase in progress? (9)
• Error: HEAD does not match expected COMMIT_SHA_CHECK' (3)
• Failed to trigger node-test-commit (3)
• error: could not apply 42fd49a4af6... build: enable Maglev for riscv64 (3)
• sh: line 1: 429:: command not found (3)
• error: could not apply 61890720c8a... add readme and initial code (2)
• test-runner/test-run-watch-cwd-isolation-none-argv (11)
• parallel/test-debugger-probe-failure-process-exit (6)
• parallel/test-npm-install (4)
• sea/test-single-executable-application-empty (3)
• client-proxy/test-https-proxy-request-invalid-char-in-url (2)
• es-module/test-typescript (2)
• parallel/test-debugger-pid (2)
• parallel/test-process-finalization (2)
• sequential/test-debugger-pid (2)
• sequential/test-watch-mode-restart-esm-loading-error (2)
• test-runner/test-run-watch-cwd-isolation-none (2)

Start with reports/2026-07-12.md and compare its details with the node-test-pull-request jobs 74645 through 74744. Review the listed build, Git, trigger, and Node test failures to determine which repeated failure is actionable. Done means the selected CI failure is addressed and no longer reproduces in the affected checks.