CI Reliability 2026-07-10

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

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

Progress

• ERROR: Error fetching remote repo 'origin' (3)
• Command "git reset --hard" returned status code 128: (2)
• sh: line 1: 429:: command not found (5)
• Failed to trigger fanned build (4)
• Failed to trigger node-test-commit (4)
• fatal: No rebase in progress? (4)
• sh: line 12: [: -gt: unary operator expected (4)
• Error: HEAD does not match expected COMMIT_SHA_CHECK' (3)
• error: could not apply 42fd49a4af6... build: enable Maglev for riscv64 (3)
• test-runner/test-run-watch-cwd-isolation-none-argv (11)
• parallel/test-debugger-probe-failure-process-exit (6)
• client-proxy/test-https-proxy-request-invalid-char-in-url (2)
• es-module/test-typescript (2)
• parallel/test-blob (2)
• parallel/test-http2-origin-set-max-size (2)
• parallel/test-npm-install (2)
• sequential/test-watch-mode-restart-esm-loading-error (2)
• test-runner/test-run-watch-cwd-isolation-none (2)

Start with reports/2026-07-10.md and the linked node-test-pull-request builds, then investigate the listed CI errors and failing tests such as test-runner/test-run-watch-cwd-isolation-none-argv. Use the generated ncu-ci walk pr command output to compare failures. Done means the reported recurring failures are resolved and the affected CI runs are green.