CI Reliability 2025-04-02

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

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

Progress

• Build timed out (after 30 minutes). Marking the build as failed. (2)
• Build timed out (after 60 minutes). Marking the build as failed. (2)
• Command "git fetch --tags --force --progress -- binary_tmp@67.158.54.159:binary_tmp.git +refs/heads/jenkins-node-test-commit-arm-fanned-4d0b4e70773:refs/remotes/jenkins_tmp/_jenkins_local_branch" returned status code 128: (2)
• Failed to trigger node-test-commit (8)
• Error: list index out of range (5)
• Unexpected token '<', ..." (2)
• pummel/test-buffer-large-size (14)
• parallel/test-file-write-stream4 (6)
• sequential/test-tls-session-timeout (4)
• pummel/test-heapdump-http2 (3)
• benchmark/test-benchmark-http2 (2)
• es-module/test-typescript-eval (2)
• parallel/test-cluster-fork-stdio (2)
• sequential/test-performance-eventloopdelay (2)

Start with reports/2025-04-02.md and the linked node-test-pull-request jobs to inspect the listed CI failures. Investigate the timeout, trigger, parsing, and named test failures individually; done means the reported failures are addressed or their progress is documented.