CI Reliability 2025-09-03

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

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

Progress

• parallel/test-inspector-network-fetch (8)
• sequential/test-performance-eventloopdelay (7)
• parallel/test-runner-run-watch (6)
• client-proxy/test-https-proxy-request-invalid-char-in-url (3)
• es-module/test-http-imports (3)
• parallel/test-esm-loader-hooks-inspect-wait (3)
• parallel/test-fs-watch-recursive-delete (2)
• parallel/test-runner-output (2)
• parallel/test-runner-watch-mode-kill-signal (2)
• sequential/test-single-executable-application (2)
• sequential/test-single-executable-application-assets (2)
• sequential/test-single-executable-application-assets-raw (2)
• sequential/test-single-executable-application-disable-experimental-sea-warning (2)
• sequential/test-single-executable-application-exec-argv (2)
• sequential/test-single-executable-application-exec-argv-empty (2)
• sequential/test-single-executable-application-exec-argv-extension-cli (2)
• sequential/test-single-executable-application-exec-argv-extension-env (2)
• sequential/test-single-executable-application-exec-argv-extension-none (2)
• sequential/test-single-executable-application-snapshot (2)
• sequential/test-single-executable-application-snapshot-and-code-cache (2)
• sequential/test-single-executable-application-snapshot-worker (2)
• sequential/test-single-executable-application-use-code-cache (2)
• wpt/test-streams (2)
• wpt/test-url (2)
• Build timed out (after 60 minutes). Marking the build as failed. (8)
• Unexpected termination of the channel (5)
• Build timed out (after 30 minutes). Marking the build as failed. (4)
• Failed to trigger sub builds (2)
• fatal error: ld terminated with signal 9 [Killed] (2)
• fatal: No rebase in progress? (2)

Start with reports/2025-09-03.md and the linked node-test-pull-request builds to inspect the failure details. Work through the listed recurring failures, beginning with the highest counts such as parallel/test-inspector-network-fetch and sequential/test-performance-eventloopdelay. Done means the identified CI failures no longer recur across the affected pull requests.