CI Reliability 2025-03-31

Failures in node-test-pull-request/65801 to node-test-pull-request/65899 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-03-31.md)

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

Progress

• 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)
• Error: list index out of range (5)
• Failed to trigger node-test-commit (5)
• error: remote GitHub already exists. (2)
• Unexpected token '<', ..." (8)
• pummel/test-buffer-large-size (14)
• parallel/test-file-write-stream4 (4)
• benchmark/test-benchmark-http2 (2)
• es-module/test-typescript-eval (2)
• parallel/test-buffer-tostring-rangeerror (2)
• parallel/test-runner-run-watch (2)
• parallel/test-stream-readable-unpipe-resume (2)
• sequential/test-performance-eventloopdelay (2)
• sequential/test-tls-session-timeout (2)

Start with reports/2025-03-31.md and the linked CI runs, using the listed failure messages to trace the affected Node.js tests. Review the unchecked failures, including the named test files, and confirm that each recurring failure is resolved in later CI runs before marking its progress complete.