CI Reliability 2025-06-28

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

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

Progress

• pummel/test-string-decoder-large-buffer (19)
• parallel/test-buffer-tostring-range (18)
• parallel/test-config-file (11)
• pummel/test-buffer-large-size-buffer-alloc-unsafe (6)
• parallel/test-stream-readable-to-web (5)
• sequential/test-performance-eventloopdelay (4)
• sequential/test-tls-session-timeout (4)
• wpt/test-streams (4)
• parallel/test-debugger-extract-function-name (3)
• parallel/test-worker-nearheaplimit-deadlock (3)
• es-module/test-vm-contextified-script-leak (2)
• parallel/test-inspector-connect-to-main-thread (2)
• parallel/test-npm-install (2)
• parallel/test-worker-message-port-transfer-filehandle (2)
• wpt/test-blob (2)
• wpt/test-webcrypto (2)
• Build timed out (after 30 minutes). Marking the build as failed. (11)
• ERROR: Error fetching remote repo 'origin' (5)
• Error: - process terminated with status 1, expected 0 (7)
• fatal: No rebase in progress? (3)

Start with reports/2025-06-28.md and the linked node-test-pull-request jobs, using the listed test names and failure messages to trace the recurring failures. The ncu-ci walk pr --stats=true --markdown reports/2025-06-28.md command shows how the report was generated; done means the listed recurring failures are addressed and the progress items can be checked off.