CI Reliability 2025-09-07

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

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

Progress

• sequential/test-single-executable-application-exec-argv-extension-cli (13)
• sequential/test-single-executable-application-exec-argv-extension-env (13)
• sequential/test-single-executable-application-exec-argv-extension-none (13)
• client-proxy/test-https-proxy-request-invalid-char-in-url (5)
• parallel/test-runner-watch-mode-kill-signal (3)
• sequential/test-performance-eventloopdelay (3)
• wpt/test-streams (3)
• parallel/test-runner-run-watch (2)
• parallel/test-worker-nearheaplimit-deadlock (2)
• pummel/test-timers (2)
• Build timed out (after 60 minutes). Marking the build as failed. (4)
• Build timed out (after 30 minutes). Marking the build as failed. (2)
• fatal: No rebase in progress? (4)
• ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)

Start with reports/2025-09-07.md in the linked reliability repository and inspect the listed CI job failures from node-test-pull-request builds 69003–69098. Use the individual failure details to identify and address the recurring causes, then verify the affected jobs no longer fail and update the progress checklist.