CI Reliability 2025-07-31

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

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

Progress

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

Start by reviewing reports/2025-07-31.md and the failures linked from node-test-pull-request/68229 through 68328. Use the listed test names and CI errors to investigate each recurring failure, beginning with the highest-count entries such as sequential/test-tls-session-timeout and wasi/test-wasi. Done means the reported recurring failures are resolved and the progress list can be updated.