CI Reliability 2025-11-21

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

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

Progress

• Backing channel 'JNLP4-connect connection from ... is disconnected. (4)
• Build timed out (after 30 minutes). Marking the build as failed. (2)
• Build timed out (after 60 minutes). Marking the build as failed. (2)
• ERROR: Error fetching remote repo 'origin' (2)
• ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
• ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ... (2)
• fatal error: Killed signal terminated program cc1plus (2)
• fatal: unable to access 'https://github.com/nodejs/build.git/': The requested URL returned error: 500 (2)
• async-hooks/test-emit-before-on-destroyed (2)
• client-proxy/test-https-proxy-request-invalid-char-in-url (2)
• parallel/test-quic-test-client (2)
• parallel/test-repl-paste-big-data (2)
• sequential/test-performance-eventloopdelay (2)
• test-runner/test-run-watch-emit-restarted (2)
• test-runner/test-run-watch-repeatedly (2)
• test-runner/test-run-watch-run-duration (2)
• test-runner/test-run-watch-without-file (2)
• wpt/test-hr-time (2)

Start with reports/2025-11-21.md and the linked node-test-pull-request runs, then inspect the listed infrastructure errors and failing tests such as async-hooks/test-emit-before-on-destroyed and test-runner/test-run-watch-restarted. The report does not identify a specific change; completion would require determining the causes and reducing the repeated CI failures.