CI Reliability 2025-03-10

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

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

Progress

• Build timed out (after 30 minutes). Marking the build as failed. (5)
• 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? (8)
• error: remote GitHub already exists. (5)
• ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (3)
• Error: list index out of range (3)
• parallel/test-runner-run-watch (8)
• sequential/test-fs-watch (8)
• parallel/test-file-write-stream4 (6)
• parallel/test-fs-watch-recursive-delete (6)
• parallel/test-buffer-tostring-rangeerror (5)
• parallel/test-debugger-heap-profiler (5)
• parallel/test-debugger-break (2)
• parallel/test-fs-cp (2)
• parallel/test-runner-output (2)
• parallel/test-zlib-brotli-16GB (2)
• sequential/test-performance-eventloopdelay (2)

Start by opening reports/2025-03-10.md and reviewing the failures linked from the CI job range in this issue. Use the generated ncu-ci walk pr --stats=true --markdown reports/2025-03-10.md command context to investigate one failure group; done means identifying and addressing the relevant CI failure with evidence from reruns.