CI Reliability 2026-08-01

Failures in node-test-pull-request/75252 to node-test-pull-request/75347 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-08-01.md)

Open https://github.com/nodejs/reliability/blob/main/reports/2026-08-01.md to see failure details

Progress

• Build timed out (after 30 minutes). Marking the build as failed. (2)
• Failed to trigger fanned build (6)
• sh: line 12: [: -gt: unary operator expected (6)
• fatal: No rebase in progress? (4)
• ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (3)
• Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified. (3)
• Failed to trigger node-test-commit (3)
• fatal error: too many errors emitted, stopping now [-ferror-limit=] (2)
• client-proxy/test-https-proxy-request-invalid-char-in-url (3)
• parallel/test-http2-reset-happy-close (2)
• parallel/test-timers-immediate-queue (2)
• parallel/test-vfs-readdir-symlink-recursive (2)

Start with reports/2026-08-01.md and the linked node-test-pull-request builds to inspect details for the recurring failures listed in the issue. Compare the affected jobs and errors, then use the Progress checklist to track investigations and document when each repeated CI failure has been addressed.