CI Reliability 2025-07-30

Failures in node-test-pull-request/68212 to node-test-pull-request/68306 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-07-30.md)

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

Progress

• Build timed out (after 30 minutes). Marking the build as failed. (4)
• fatal: No rebase in progress? (5)
• sh: line 1: 429:: command not found (4)
• Error: - process terminated with status 1, expected 0 (2)
• Unknown (2)
• wasi/test-wasi (11)
• sequential/test-tls-session-timeout (9)
• wpt/test-web-locks (8)
• parallel/test-http-keep-alive-empty-line (7)
• parallel/test-runner-mock-timers-scheduler (7)
• parallel/test-stream-readable-to-web (7)
• parallel/test-http-outgoing-end-cork (6)
• sequential/test-performance-eventloopdelay (6)
• parallel/test-http-server-headers-timeout-keepalive (4)
• client-proxy/test-http-proxy-request-connection-refused (3)
• parallel/test-cli-eval (3)
• parallel/test-cli-node-print-help (3)
• parallel/test-fs-stat-bigint (3)
• client-proxy/test-https-proxy-request-connection-refused (2)
• client-proxy/test-https-proxy-request-invalid-char-in-url (2)
• es-module/test-vm-contextified-script-leak (2)
• parallel/test-http-client-close-with-default-agent (2)
• parallel/test-http2-forget-closed-streams (2)
• parallel/test-runner-output (2)
• parallel/test-runner-run-watch (2)
• parallel/test-without-async-context-frame (2)
• sequential/test-perf-hooks (2)
• wpt/test-blob (2)

Start with reports/2025-07-30.md and the linked node-test-pull-request runs, then use the listed failure signatures and test names to group recurring causes. Check the ncu-ci walk command context shown in the issue. Done means the tracked failures are investigated and the progress items have a clear outcome.