CI Reliability 2025-09-08

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

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

Progress

• sequential/test-single-executable-application-exec-argv-extension-cli (12)
• sequential/test-single-executable-application-exec-argv-extension-env (12)
• sequential/test-single-executable-application-exec-argv-extension-none (12)
• wpt/test-streams (4)
• client-proxy/test-https-proxy-request-invalid-char-in-url (3)
• parallel/test-runner-watch-mode-kill-signal (3)
• async-hooks/test-emit-before-on-destroyed (2)
• parallel/test-runner-run-watch (2)
• parallel/test-worker-nearheaplimit-deadlock (2)
• pummel/test-timers (2)
• 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)
• fatal error: Killed signal terminated program cc1plus (2)

Start with the linked reports/2025-09-08.md report and the ncu-ci walk pr --stats=true --markdown reports/2025-09-08.md output. Review the listed failing tests and CI errors to identify their causes. Done means the failures are addressed and the Progress entries can be checked off.