CI Reliability 2025-03-18

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

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

Progress

• Build timed out (after 30 minutes). Marking the build as failed. (4)
• fatal error: Killed signal terminated program cc1plus (9)
• error: remote GitHub already exists. (8)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (7)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_turboshaft.vcxproj] (6)
• ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ... (4)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows-debug\node\tools\v8_gypfiles\v8_turboshaft.vcxproj] (4)
• Error: - process terminated with status 1, expected 0 (3)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_turboshaft_host.vcxproj] (3)
• ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_base_without_compiler.vcxproj] (2)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_compiler.vcxproj] (2)
• pummel/test-buffer-large-size (8)
• parallel/test-stream-readable-unpipe-resume (5)
• node-api/test_threadsafe_function/test (3)
• parallel/test-buffer-tostring-rangeerror (3)
• parallel/test-file-write-stream4 (2)
• parallel/test-runner-run-watch (2)
• parallel/test-zlib-convenience-methods (2)
• sequential/test-perf-hooks (2)
• sequential/test-performance-eventloopdelay (2)
• sequential/test-tls-session-timeout (2)

Start with reports/2025-03-18.md and the linked node-test-pull-request builds, then compare the listed failures with the generated ncu-ci walk pr --stats=true --markdown reports/2025-03-18.md output. Review the Progress checklist and CI logs for each repeated failure. Done means the failures are resolved or have clear follow-up issues.