CI Reliability 2025-09-11

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

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

Progress

• parallel/test-without-async-context-frame (6)
• wpt/test-streams (6)
• parallel/test-runner-run-watch (5)
• async-hooks/test-emit-before-on-destroyed (4)
• client-proxy/test-https-proxy-request-invalid-char-in-url (3)
• sequential/test-performance-eventloopdelay (3)
• parallel/test-zlib-brotli-16GB (2)
• sequential/test-single-executable-application (2)
• sequential/test-single-executable-application-asset-keys (2)
• sequential/test-single-executable-application-asset-keys-empty (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-inspect (2)
• sequential/test-single-executable-application-inspect-in-sea-flags (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)
• Failed to create a temp file on /home/iojs/build/workspace/node (5)
• fatal: No rebase in progress? (4)
• fatal error: Killed signal terminated program cc1plus (3)
• fatal error: ld terminated with signal 9 [Killed] (2)

Review reports/2025-09-11.md and the linked node-test-pull-request runs, starting with the listed failures. Reproduce the affected tests or build failures and trace each cause before deciding what changes are needed. Done means the recurring failures are addressed and the relevant CI runs no longer fail.