CI Reliability 2025-04-26

Failures in node-test-pull-request/66364 to node-test-pull-request/66463 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-04-26.md)

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

Progress

• Build timed out (after 30 minutes). Marking the build as failed. (4)
• Failed to trigger node-test-commit (7)
• error: remote GitHub already exists. (2)
• fatal: No rebase in progress? (2)
• parallel/test-repl-import-referrer (10)
• parallel/test-http2-options-max-headers-block-length (8)
• parallel/test-buffer-tostring-rangeerror (4)
• sequential/test-performance-eventloopdelay (4)
• parallel/test-stream-readable-unpipe-resume (3)
• parallel/test-without-async-context-frame (3)
• sequential/test-tls-session-timeout (3)
• parallel/test-debugger-break (2)
• parallel/test-file-write-stream4 (2)
• parallel/test-http2-close-while-writing (2)
• parallel/test-whatwg-url-canparse (2)
• parallel/test-zlib-brotli-flush (2)

Start with reports/2025-04-26.md and the linked node-test-pull-request/66364 through /66463 CI runs. Review the listed timeout, trigger, Git, and test failures to identify which failures are actionable and reproduce them through the relevant CI entry points. Done means the recurring failures are fixed or separately tracked and the affected CI jobs become reliable.