CI Reliability 2026-07-26

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

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

Progress

• parallel/test-repl-user-error-handler (19)
• client-proxy/test-https-proxy-request-invalid-char-in-url (3)
• parallel/test-debugger-probe-failure-process-exit (3)
• parallel/test-runner-run-watch (3)
• parallel/test-runner-watch-mode (3)
• parallel/test-vfs-readdir-symlink-recursive (3)
• sequential/test-performance-eventloopdelay (3)
• sea/test-single-executable-application-disable-experimental-sea-warning (2)
• test-runner/test-run-watch-emit-restarted (2)
• ERROR: Error fetching remote repo 'origin' (5)
• Command "git fetch --no-tags --force --progress -- git@github.com:nodejs/node.git +refs/heads/*:refs/remotes/origin/* +refs/pull/64399/head:refs/remotes/origin/_jenkins_local_branch" returned status code 128: (2)
• fatal: No rebase in progress? (16)
• error: could not apply 61890720c8a... add readme and initial code (14)
• Failed to trigger fanned build (9)
• 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)

Start with reports/2026-07-26.md and the linked node-test-pull-request runs, then review the listed failing tests and Jenkins or git errors. The work is complete when the identified recurring failures are addressed and the affected CI runs no longer reproduce them.