CI Reliability 2025-01-28

Failures in node-test-pull-request/64685 to node-test-pull-request/64778 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-01-28.md)

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

Progress

• parallel/test-permission-fs-read (21)
• parallel/test-permission-fs-write (21)
• parallel/test-fs-cp (14)
• parallel/test-cluster-fork-stdio (9)
• parallel/test-cluster-concurrent-disconnect (6)
• parallel/test-net-write-fully-async-hex-string (6)
• parallel/test-without-async-context-frame (6)
• es-module/test-wasm-web-api (5)
• parallel/test-cluster-disconnect-unshared-tcp (4)
• parallel/test-net-write-fully-async-buffer (4)
• parallel/test-watch-mode-files_watcher (4)
• parallel/test-buffer-tostring-rangeerror (3)
• parallel/test-esm-loader-hooks-inspect-wait (3)
• parallel/test-file-write-stream4 (2)
• parallel/test-fs-watch-recursive-delete (2)
• parallel/test-stream-readable-unpipe-resume (2)
• Build timed out (after 30 minutes). Marking the build as failed. (5)
• ERROR: Error fetching remote repo 'origin' (3)
• Error: invalid syntax (3)
• fatal: No rebase in progress? (3)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (2)
• sh: line 12: [: -gt: unary operator expected (2)

Start by reviewing reports/2025-01-28.md and the linked node-test-pull-request builds for the repeated failures. Investigate the listed test names and CI errors, then verify that the relevant failures are resolved and the CI green rate improves.