CI Reliability 2026-07-27

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

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

Progress

• parallel/test-repl-user-error-handler (10)
• parallel/test-debugger-probe-failure-process-exit (3)
• parallel/test-vfs-readdir-symlink-recursive (3)
• parallel/test-crypto-x509 (2)
• sea/test-single-executable-application-disable-experimental-sea-warning (2)
• sequential/test-performance-eventloopdelay (2)
• test-runner/test-run-watch-emit-restarted (2)
• ERROR: Error fetching remote repo 'origin' (4)
• 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)
• Failed to trigger fanned build (28)
• error: could not apply 61890720c8a... add readme and initial code (16)
• fatal: No rebase in progress? (14)
• error: could not apply 4f844f4380a... repl: use inspector over vm (4)
• 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-27.md linked in the issue, then inspect the listed failures such as parallel/test-repl-user-error-handler and test-runner/test-run-watch-emit-restarted. Use the report details to determine which failures are actionable; the work is done when the relevant entries in the Progress list are resolved and checked off.