CI Reliability 2026-07-13

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

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

Progress

• ERROR: Error fetching remote repo 'origin' (2)
• fatal: No rebase in progress? (10)
• Failed to trigger node-test-commit (4)
• error: could not apply 42fd49a4af6... build: enable Maglev for riscv64 (3)
• error: could not apply 61890720c8a... add readme and initial code (3)
• sh: line 1: 429:: command not found (2)
• parallel/test-debugger-probe-failure-process-exit (6)
• test-runner/test-run-watch-cwd-isolation-none-argv (5)
• parallel/test-npm-install (4)
• sea/test-single-executable-application-empty (4)
• parallel/test-process-finalization (3)
• client-proxy/test-https-proxy-request-invalid-char-in-url (2)
• parallel/test-debugger-pid (2)
• parallel/test-perf-hooks-eventlooputilization (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-13.md and the linked node-test-pull-request jobs, then review the listed error messages and failing tests such as parallel/test-npm-install and test-runner/test-run-watch-cwd-isolation-none. Use the ncu-ci walk output to correlate failures across pull requests. Done means the tracked CI failure causes have been addressed and the corresponding progress items can be checked off.