CI Reliability 2025-02-01

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

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

Progress

• Build timed out (after 30 minutes). Marking the build as failed. (2)
• ERROR: Error fetching remote repo 'origin' (2)
• Unknown (2)
• parallel/test-assert-fail (8)
• parallel/test-runner-run-watch (7)
• parallel/test-net-write-fully-async-buffer (6)
• parallel/test-permission-fs-read (6)
• parallel/test-permission-fs-write (6)
• parallel/test-buffer-tostring-rangeerror (5)
• parallel/test-runner-output (5)
• wpt/test-url (4)
• parallel/test-cluster-fork-stdio (3)
• parallel/test-file-write-stream4 (3)
• parallel/test-net-write-fully-async-hex-string (3)
• wpt/test-compression (3)
• parallel/test-buffer-tostring-range (2)
• parallel/test-child-process-bad-stdio (2)
• parallel/test-esm-loader-hooks-inspect-wait (2)
• parallel/test-fs-cp (2)
• parallel/test-pipe-file-to-http (2)
• parallel/test-stream-readable-unpipe-resume (2)
• pummel/test-heapdump-http2 (2)
• fatal: No rebase in progress? (4)

Start with reports/2025-02-01.md and the linked CI runs from node-test-pull-request/64792 through 64886. Use the listed failure names and the ncu-ci walk pr command to investigate recurring failures; done means the reported CI failures have been addressed and the relevant checks are reliable again.