CI Reliability 2025-10-07

Failures in node-test-pull-request/69486 to node-test-pull-request/69584 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-10-07.md)

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

Progress

• Unexpected termination of the channel (8)
• Build timed out (after 30 minutes). Marking the build as failed. (5)
• fatal: detected dubious ownership in repository at 'C:/workspace/node-test-binary-windows-js-suites/build' (5)
• Failed to trigger node-test-commit (3)
• ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (2)
• parallel/test-runner-run-watch (15)
• parallel/test-without-async-context-frame (10)
• parallel/test-runner-watch-mode-kill-signal (8)
• client-proxy/test-https-proxy-request-invalid-char-in-url (4)
• parallel/test-runner-run (4)
• sequential/test-perf-hooks (4)
• sequential/test-worker-prof (3)
• wpt/test-streams (3)
• parallel/test-http2-close-while-writing (2)
• parallel/test-quic-test-client (2)
• parallel/test-worker-nearheaplimit-deadlock (2)
• wpt/test-hr-time (2)

Start with reports/2025-10-07.md and the linked node-test-pull-request Jenkins runs, then group the failures listed under Progress by their reported errors and test names. Review the relevant CI job output and existing reliability tooling before choosing a focused failure. Done means the identified failures are resolved or otherwise tracked with evidence that the affected CI runs are reliable.