CI Reliability 2026-08-19

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

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

Progress

• Build timed out (after 120 minutes). Marking the build as failed. (2)
• Build timed out (after 30 minutes). Marking the build as failed. (2)
• fatal: No rebase in progress? (12)
• error: could not apply 61890720c8a... add readme and initial code (10)
• fatal: no rebase in progress (5)
• sh: line 1: 429:: command not found (4)
• 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)
• Failed to trigger node-test-commit (2)
• Unknown (4)
• parallel/test-stream-pipeline-http2 (12)
• sequential/test-debugger-pid (6)
• parallel/test-inspect-async-hook-setup-at-inspect (5)
• sea/test-single-executable-application-assets-raw (5)
• sea/test-single-executable-application-esm-code-cache (5)
• sea/test-build-sea (4)
• sea/test-build-sea-already-exists (4)
• sea/test-build-sea-custom-argv0 (4)
• sea/test-build-sea-executable-field (4)
• sea/test-build-sea-missing-output (4)
• sea/test-single-executable-application-asset-keys (4)
• sea/test-single-executable-application-asset-keys-empty (4)
• sea/test-single-executable-application-assets (4)
• sea/test-single-executable-application-disable-experimental-sea-warning (4)
• sea/test-single-executable-application-empty (4)
• sea/test-single-executable-application-exec-argv (4)
• sea/test-single-executable-application-exec-argv-empty (4)
• sea/test-single-executable-application-exec-argv-extension-cli (4)
• sea/test-single-executable-application-exec-argv-extension-env (4)
• sequential/test-performance-eventloopdelay (4)
• sea/test-single-executable-application-esm (3)
• sea/test-single-executable-application-exec-argv-extension-none (3)
• sea/test-single-executable-application-inspect (3)
• parallel/test-bootstrap-modules (2)
• parallel/test-debugger-extract-function-name (2)
• parallel/test-inspector-connect-to-main-thread (2)
• parallel/test-runner-run (2)
• sea/test-single-executable-application-inspect-in-sea-flags (2)
• test-runner/test-run-watch-cwd-isolation-none (2)
• test-runner/test-run-watch-emit-restarted (2)

Start with reports/2026-08-19.md and the linked node-test-pull-request builds, using the listed failure messages and test names to group the failures. Review the command that generated the report, ncu-ci walk pr --stats=true --markdown reports/2026-08-19.md, then investigate each recurring failure. Done means the listed CI failures are addressed and the corresponding Progress entries can be checked off.