CI Reliability 2026-07-11

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

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

Progress

• Build timed out (after 60 minutes). Marking the build as failed. (2)
• ERROR: Error fetching remote repo 'origin' (4)
• Command "git reset --hard" returned status code 128: (2)
• fatal: No rebase in progress? (6)
• sh: line 1: 429:: command not found (5)
• 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)
• Failed to trigger fanned build (2)
• sh: line 12: [: -gt: unary operator expected (2)
• test-runner/test-run-watch-cwd-isolation-none-argv (11)
• parallel/test-debugger-probe-failure-process-exit (7)
• parallel/test-npm-install (4)
• client-proxy/test-https-proxy-request-invalid-char-in-url (2)
• es-module/test-typescript (2)
• sequential/test-watch-mode-restart-esm-loading-error (2)
• test-runner/test-run-watch-cwd-isolation-none (2)

Start with reports/2026-07-11.md and the linked node-test-pull-request builds, then use the listed failure messages and test names to group the recurring CI problems. Check the ncu-ci walk command context and investigate each unchecked item. Done means the identified failures are addressed and the affected PR builds become reliable again.