CI Reliability 2025-06-18

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

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

Progress

• parallel/test-buffer-tostring-range (17)
• pummel/test-string-decoder-large-buffer (15)
• parallel/test-fs-watch-recursive-delete (11)
• parallel/test-fs-write-buffer-large (11)
• pummel/test-buffer-large-size-buffer-alloc-unsafe (6)
• parallel/test-config-file (5)
• parallel/test-fs-write-file-invalid-path (4)
• pummel/test-buffer-large-size-buffer-alloc-unsafe-slow (4)
• pummel/test-buffer-large-size-slowbuffer (4)
• sequential/test-tls-session-timeout (4)
• pummel/test-buffer-large-size-buffer-alloc (3)
• pummel/test-buffer-large-size-buffer-write (3)
• es-module/test-vm-contextified-script-leak (2)
• parallel/test-fs-write-negativeoffset (2)
• parallel/test-http2-close-while-writing (2)
• parallel/test-stream-readable-to-web (2)
• sequential/test-performance-eventloopdelay (2)
• Build timed out (after 30 minutes). Marking the build as failed. (6)
• Build timed out (after 60 minutes). Marking the build as failed. (2)
• fatal error: Killed signal terminated program cc1plus (3)
• Failed to trigger node-test-commit (2)
• sh: line 12: [: -gt: unary operator expected (2)

Start with reports/2025-06-18.md and the linked CI jobs for the listed failures. Review the generated output from ncu-ci walk pr --stats=true --markdown reports/2025-06-18.md, then investigate each recurring test or infrastructure failure. Done means the identified failures are resolved and the progress checklist is updated.