CI Reliability 2025-03-17

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

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

Progress

• Build timed out (after 30 minutes). Marking the build as failed. (4)
• error: remote GitHub already exists. (9)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (8)
• fatal error: Killed signal terminated program cc1plus (7)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows-debug\node\tools\v8_gypfiles\v8_turboshaft.vcxproj] (4)
• ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ... (3)
• 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.vcxproj] (3)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_turboshaft_host.vcxproj] (3)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_compiler.vcxproj] (2)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers_host.vcxproj] (2)
• pummel/test-buffer-large-size (7)
• parallel/test-stream-readable-unpipe-resume (4)
• node-api/test_threadsafe_function/test (3)
• parallel/test-buffer-tostring-rangeerror (3)
• sequential/test-performance-eventloopdelay (3)
• parallel/test-pipe-file-to-http (2)
• sequential/test-perf-hooks (2)
• sequential/test-tls-session-timeout (2)

Start with the linked node-test-pull-request jobs and the generated reports/2025-03-17.md report. Review the repeated timeout, GitHub remote, compiler-memory, workspace, and test failures to determine which are actionable. Done means the identified CI failure causes are addressed and subsequent pull-request jobs no longer reproduce them.