CI Reliability 2026-05-15

Failures in node-test-pull-request/73355 to node-test-pull-request/73453 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-15.md)

Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-15.md to see failure details

Progress

• ERROR: Error fetching remote repo 'origin' (3)
• sh: line 12: [: -gt: unary operator expected (10)
• fatal: No rebase in progress? (5)
• Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified. (4)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (4)
• ERROR: out of memory (3)
• ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (2)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers_host.vcxproj] (2)
• error: remote GitHub already exists. (2)
• sequential/test-watch-mode-worker (10)
• parallel/test-zlib-brotli-16GB (5)
• parallel/test-http2-close-while-writing (3)
• parallel/test-memory-usage (3)
• async-hooks/test-emit-after-on-destroyed (2)
• async-hooks/test-statwatcher (2)
• client-proxy/test-http-proxy-request-connection-refused (2)
• parallel/test-process-finalization (2)
• sequential/test-performance-eventloopdelay (2)
• test-runner/test-output-test-runner-watch-spec (2)
• test-runner/test-run-watch-dependency-repeatedly (2)
• test-runner/test-run-watch-emit-restarted (2)

Start with reports/2026-05-15.md and the listed node-test-pull-request failures, then use the generated ncu-ci walk pr --stats=true --markdown reports/2026-05-15.md command to understand how the report was produced. Investigate each recurring error or test failure, including the named watch-mode, zlib, HTTP/2, memory, and test-runner cases. Done means the reported recurring failures are addressed and CI becomes green again.