CI Reliability 2026-08-20

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

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

Progress

• Build timed out (after 60 minutes). Marking the build as failed. (6)
• Build timed out (after 30 minutes). Marking the build as failed. (2)
• fatal: No rebase in progress? (8)
• error: could not apply 61890720c8a... add readme and initial code (6)
• sh: line 1: 429:: command not found (5)
• Failed to trigger node-test-commit (4)
• ERROR: out of memory (3)
• Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified. (3)
• ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
• fatal: no rebase in progress (2)
• sh: line 12: [: -gt: unary operator expected (2)
• Unknown (3)
• parallel/test-stream-pipeline-http2 (9)
• sequential/test-debugger-pid (6)
• test-runner/test-run-watch-emit-restarted (5)
• parallel/test-fastutf8stream-reopen (4)
• parallel/test-inspect-async-hook-setup-at-inspect (4)
• parallel/test-debugger-extract-function-name (3)
• sequential/test-watch-mode-restart-esm-loading-error (3)
• parallel/test-bootstrap-modules (2)
• parallel/test-runner-run (2)
• sea/test-single-executable-application-esm-code-cache (2)
• sea/test-single-executable-application-exec-argv-extension-cli (2)
• sea/test-single-executable-application-exec-argv-extension-env (2)

Open reports/2026-08-20.md and review the linked node-test-pull-request builds from 75920 through 76013. Use the listed failure messages and test names to investigate each recurring CI failure; done is reflected by resolving the relevant progress items and improving the reported CI results.