CI Reliability 2025-09-05

Failures in node-test-pull-request/68964 to node-test-pull-request/69062 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-09-05.md)

Open https://github.com/nodejs/reliability/blob/main/reports/2025-09-05.md to see failure details

Progress

• sequential/test-single-executable-application-exec-argv-extension-cli (11)
• sequential/test-single-executable-application-exec-argv-extension-env (11)
• sequential/test-single-executable-application-exec-argv-extension-none (11)
• sequential/test-performance-eventloopdelay (6)
• client-proxy/test-https-proxy-request-invalid-char-in-url (4)
• parallel/test-runner-watch-mode-kill-signal (4)
• es-module/test-http-imports (3)
• parallel/test-runner-run-watch (3)
• parallel/test-esm-loader-hooks-inspect-wait (2)
• parallel/test-fs-watch-recursive-delete (2)
• parallel/test-inspector-network-fetch (2)
• parallel/test-runner-output (2)
• pummel/test-timers (2)
• Build timed out (after 60 minutes). Marking the build as failed. (4)
• Unexpected termination of the channel (3)
• Build timed out (after 30 minutes). Marking the build as failed. (2)
• fatal: No rebase in progress? (3)
• ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)

Review reports/2025-09-05.md and the Jenkins jobs from node-test-pull-request/68964 through 69062 to identify the failure details. Start with the listed sequential, parallel, client-proxy, es-module, pummel, timeout, and channel failures. Done means the reported recurring failures are addressed and the affected CI runs become reliable.