CI Reliability 2025-04-16

Failures in node-test-pull-request/66191 to node-test-pull-request/66291 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-16.md)

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

Progress

• parallel/test-runner-plan (8)
• parallel/test-file-write-stream4 (4)
• parallel/test-debugger-heap-profiler (3)
• sequential/test-tls-session-timeout (3)
• parallel/test-buffer-tostring-rangeerror (2)
• parallel/test-debugger-break (2)
• parallel/test-stream-readable-unpipe-resume (2)
• pummel/test-buffer-large-size (2)
• sequential/test-performance-eventloopdelay (2)
• Build timed out (after 30 minutes). Marking the build as failed. (4)
• Build timed out (after 60 minutes). Marking the build as failed. (3)
• error C2065: 'NoArrayBufferZeroFillScope': undeclared identifier [C:\workspace\node-compile-windows\node\libnode.vcxproj] (10)
• Error: list index out of range (9)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (6)
• error: remote GitHub already exists. (4)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows-debug\node\tools\v8_gypfiles\v8_turboshaft.vcxproj] (3)
• ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
• ERROR: The process with PID 9828 (child process of PID 10148) could not be terminated. (2)
• Failed to trigger node-test-commit (2)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_turboshaft_host.vcxproj] (2)
• fatal: No rebase in progress? (2)

Start with reports/2025-04-16.md and the linked node-test-pull-request build range; the report was generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-16.md. Review the listed test, build, and infrastructure failures, but note that the issue does not define a single change or completion criterion.