CI Reliability 2026-04-24

Failures in node-test-pull-request/72799 to node-test-pull-request/72896 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-24.md)

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

Progress

• parallel/test-debugger-probe-json-preview (12)
• parallel/test-debugger-probe-miss (10)
• wpt/test-wasm-jsapi (10)
• parallel/test-debugger-probe-child-inspect-port-zero (8)
• parallel/test-debugger-probe-global-option-order (7)
• parallel/test-debugger-probe-json-special-values (7)
• wpt/test-hr-time (7)
• parallel/test-debugger-probe-json (6)
• parallel/test-debugger-probe-text (6)
• sequential/test-watch-mode-restart-esm-loading-error (6)
• test-runner/test-run-watch-dependency-repeatedly (6)
• test-runner/test-run-watch-without-file (5)
• test-runner/test-run-watch-cwd-isolation-none (4)
• test-runner/test-run-watch-run-duration (4)
• parallel/test-watch-mode-files_watcher (3)
• test-runner/test-run-watch-repeatedly (3)
• client-proxy/test-https-proxy-request-invalid-char-in-url (2)
• parallel/test-http2-close-while-writing (2)
• pummel/test-repl-paste-big-data (2)
• sequential/test-debugger-pid (2)
• sequential/test-performance-eventloopdelay (2)
• test-runner/test-output-test-runner-watch-spec (2)
• Build timed out (after 60 minutes). Marking the build as failed. (2)
• ERROR: Error fetching remote repo 'origin' (2)
• fatal: No rebase in progress? (3)
• ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (2)
• Failed to trigger fanned build (2)
• sh: line 1: 404:: command not found (2)

Start by opening reports/2026-04-24.md and reviewing the Jenkins failures from node-test-pull-request/72799 through 72896. Then investigate the listed failing tests or CI errors, using their test paths as entry points. Done means the identified recurring failures are resolved or otherwise explained and the corresponding progress items can be checked off.