CI Reliability 2025-03-08

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

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

Progress

• Build timed out (after 30 minutes). Marking the build as failed. (4)
• Failed to create a temp file on C:\workspace\node-compile-windows (3)
• ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (9)
• Error: list index out of range (3)
• ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
• Failed to trigger sub builds (2)
• error: remote GitHub already exists. (2)
• parallel/test-assert-fail (12)
• parallel/test-runner-run-watch (11)
• parallel/test-file-write-stream4 (6)
• parallel/test-buffer-tostring-rangeerror (3)
• parallel/test-debugger-heap-profiler (3)
• sequential/test-performance-eventloopdelay (3)
• parallel/test-fs-cp (2)
• parallel/test-zlib-brotli-16GB (2)

Start with reports/2025-03-08.md and the linked node-test-pull-request builds 65539–65637; use the listed failure messages and test names to separate infrastructure failures from test failures. The issue does not define a single change or completion criterion, so resolution would require determining which failures are actionable and verifying the affected CI jobs become reliable.