CI Reliability 2025-01-31

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

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

Progress

• parallel/test-permission-fs-read (15)
• parallel/test-permission-fs-write (15)
• parallel/test-fs-cp (8)
• parallel/test-net-write-fully-async-hex-string (7)
• parallel/test-assert-fail (5)
• parallel/test-net-write-fully-async-buffer (5)
• parallel/test-file-write-stream4 (4)
• parallel/test-runner-output (4)
• parallel/test-runner-run-watch (4)
• wpt/test-url (4)
• parallel/test-cluster-fork-stdio (3)
• parallel/test-watch-mode-files_watcher (3)
• parallel/test-child-process-bad-stdio (2)
• parallel/test-esm-loader-hooks-inspect-wait (2)
• parallel/test-fs-watch-recursive-add-file-with-url (2)
• parallel/test-pipe-file-to-http (2)
• parallel/test-stream-readable-unpipe-resume (2)
• parallel/test-zlib-brotli-16GB (2)
• pummel/test-heapdump-http2 (2)
• wpt/test-timers (2)
• Build timed out (after 30 minutes). Marking the build as failed. (4)
• ERROR: Error fetching remote repo 'origin' (2)
• fatal: No rebase in progress? (3)
• sh: line 12: [: -gt: unary operator expected (2)
• Unknown (2)

Start with the linked reliability report at reports/2025-01-31.md and inspect the listed failing jobs, beginning with the highest-count parallel/test-permission-fs-read failure. Reproduce the reported CI failures and trace each one to its relevant test or build step; done means the recurring failures are addressed and the affected jobs return to green.