CI Reliability 2025-09-27

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

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

Progress

• Build timed out (after 60 minutes). Marking the build as failed. (6)
• Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
• Build timed out (after 30 minutes). Marking the build as failed. (2)
• Unexpected termination of the channel (2)
• ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (3)
• Failed to trigger node-test-commit (2)
• fatal: No rebase in progress? (2)
• sequential/test-single-executable-application (24)
• sequential/test-single-executable-application-asset-keys (24)
• sequential/test-single-executable-application-asset-keys-empty (24)
• sequential/test-single-executable-application-assets (24)
• sequential/test-single-executable-application-assets-raw (24)
• sequential/test-single-executable-application-disable-experimental-sea-warning (24)
• sequential/test-single-executable-application-exec-argv (24)
• sequential/test-single-executable-application-exec-argv-empty (24)
• sequential/test-single-executable-application-exec-argv-extension-cli (24)
• sequential/test-single-executable-application-exec-argv-extension-env (24)
• sequential/test-single-executable-application-exec-argv-extension-none (24)
• sequential/test-single-executable-application-inspect (24)
• sequential/test-single-executable-application-inspect-in-sea-flags (24)
• sequential/test-single-executable-application-snapshot (24)
• sequential/test-single-executable-application-snapshot-and-code-cache (24)
• sequential/test-single-executable-application-snapshot-worker (24)
• sequential/test-single-executable-application-use-code-cache (24)
• parallel/test-runner-run-watch (17)
• client-proxy/test-https-proxy-request-invalid-char-in-url (7)
• parallel/test-without-async-context-frame (7)
• parallel/test-runner-watch-mode-kill-signal (6)
• sequential/test-perf-hooks (6)
• parallel/test-fs-promises-watch-iterator (3)
• parallel/test-http2-close-while-writing (3)
• sequential/test-performance-eventloopdelay (3)
• parallel/test-repl-paste-big-data (2)
• parallel/test-runner-run (2)
• wasi/test-wasi-pthread (2)
• wpt/test-hr-time (2)
• wpt/test-streams (2)
• wpt/test-webcrypto (2)

Start with reports/2025-09-27.md and the linked node-test-pull-request builds, then review the failures listed in the Progress section. Focus on identifying the cause of the repeated CI and test failures; done means the relevant failures are resolved and the affected pull requests can pass reliably.