CI Reliability 2025-06-27

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

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

Progress

• pummel/test-string-decoder-large-buffer (18)
• parallel/test-buffer-tostring-range (15)
• parallel/test-config-file (12)
• pummel/test-buffer-large-size-buffer-alloc-unsafe (7)
• parallel/test-npm-install (5)
• sequential/test-tls-session-timeout (4)
• wpt/test-streams (4)
• parallel/test-debugger-extract-function-name (3)
• parallel/test-stream-readable-to-web (3)
• parallel/test-worker-nearheaplimit-deadlock (3)
• pummel/test-buffer-large-size-buffer-write (3)
• sequential/test-performance-eventloopdelay (3)
• es-module/test-vm-contextified-script-leak (2)
• pummel/test-buffer-large-size-buffer-alloc (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 (8)
• fatal: No rebase in progress? (3)

Start with reports/2025-06-27.md and the linked node-test-pull-request jobs, then inspect the named test failures and build errors. Compare each repeated failure with its CI output and update the progress list as causes are addressed; done means the listed reliability problems are resolved or tracked with a clear follow-up.