CI Reliability 2025-07-29

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

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

Progress

• Build timed out (after 30 minutes). Marking the build as failed. (6)
• fatal: No rebase in progress? (9)
• ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (2)
• Error: - process terminated with status 1, expected 0 (2)
• wasi/test-wasi (16)
• wpt/test-web-locks (12)
• parallel/test-http-keep-alive-empty-line (10)
• parallel/test-http-outgoing-end-cork (7)
• sequential/test-performance-eventloopdelay (7)
• parallel/test-runner-mock-timers-scheduler (6)
• parallel/test-stream-readable-to-web (6)
• es-module/test-vm-contextified-script-leak (4)
• parallel/test-http-server-headers-timeout-keepalive (4)
• wpt/test-streams (4)
• parallel/test-fs-stat-bigint (3)
• parallel/test-runner-output (3)
• parallel/test-http-client-close-with-default-agent (2)
• parallel/test-runner-run-watch (2)
• parallel/test-worker-message-port-transfer-filehandle (2)
• sequential/test-tls-session-timeout (2)
• wpt/test-blob (2)

Start with the generated report at reports/2025-07-29.md and the ncu-ci walk pr --stats=true --markdown command, then inspect the linked CI runs for the listed failure patterns. The issue is done when the underlying CI failures are investigated and addressed, with the affected checks becoming reliable across subsequent PR runs.