CI Reliability 2025-06-17

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

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

Progress

• parallel/test-buffer-tostring-range (12)
• pummel/test-string-decoder-large-buffer (9)
• parallel/test-fs-watch-recursive-delete (6)
• parallel/test-fs-write-buffer-large (6)
• parallel/test-config-file (5)
• parallel/test-stream-readable-to-web (5)
• sequential/test-tls-session-timeout (4)
• parallel/test-without-async-context-frame (3)
• pummel/test-buffer-large-size-buffer-alloc (3)
• pummel/test-buffer-large-size-buffer-alloc-unsafe (3)
• pummel/test-buffer-large-size-buffer-write (3)
• parallel/test-fs-write-file-invalid-path (2)
• parallel/test-fs-write-negativeoffset (2)
• parallel/test-http2-close-while-writing (2)
• sequential/test-performance-eventloopdelay (2)
• Build timed out (after 30 minutes). Marking the build as failed. (2)
• Build timed out (after 60 minutes). Marking the build as failed. (2)
• ERROR: Error fetching remote repo 'origin' (2)
• fatal error: Killed signal terminated program cc1plus (4)
• Failed to trigger node-test-commit (2)
• sh: line 12: [: -gt: unary operator expected (2)

Start with reports/2025-06-17.md in the nodejs/reliability repository and review the linked CI run range. Investigate the listed failures, including the named test files and build errors, to identify which issues remain actionable. Done means the tracked failures have been addressed or their status is documented.