CI Reliability 2025-03-09

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

Open https://github.com/nodejs/reliability/blob/main/reports/2025-03-09.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? (9)
• error: remote GitHub already exists. (4)
• 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 (9)
• parallel/test-buffer-tostring-rangeerror (5)
• parallel/test-debugger-heap-profiler (5)
• parallel/test-file-write-stream4 (5)
• parallel/test-fs-watch-recursive-delete (4)
• sequential/test-fs-watch (4)
• 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 with the linked node-test-pull-request builds and the reliability report at reports/2025-03-09.md, using the listed failure messages and tests to group the failures. This is a generated failure inventory rather than a scoped change, so completion requires identifying and addressing the relevant CI or test causes; no single done criterion is stated.