CI Reliability 2026-06-05

Failures in node-test-pull-request/73816 to node-test-pull-request/73914 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-06-05.md)

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

Progress

• ERROR: Error fetching remote repo 'origin' (5)
• Failed to trigger sub builds (7)
• Failed to trigger fanned build (4)
• fatal: No rebase in progress? (3)
• ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (2)
• Error: Timed out waiting for restart (2)
• parallel/test-fs-watch-recursive-delete (3)
• sea/test-build-sea (3)
• sea/test-build-sea-already-exists (3)
• sea/test-build-sea-custom-argv0 (3)
• sea/test-build-sea-executable-field (3)
• sea/test-build-sea-missing-output (3)
• sea/test-single-executable-application-asset-keys (3)
• sea/test-single-executable-application-asset-keys-empty (3)
• sea/test-single-executable-application-exec-argv-extension-cli (3)
• sea/test-single-executable-application-exec-argv-extension-env (3)
• sea/test-single-executable-application-inspect (3)
• parallel/test-cluster-dgram-reuse (2)
• sea/test-single-executable-application-assets (2)
• sea/test-single-executable-application-assets-raw (2)
• sea/test-single-executable-application-disable-experimental-sea-warning (2)
• sea/test-single-executable-application-empty (2)
• sea/test-single-executable-application-esm (2)
• sea/test-single-executable-application-esm-code-cache (2)
• sea/test-single-executable-application-exec-argv (2)
• sea/test-single-executable-application-exec-argv-empty (2)
• sea/test-single-executable-application-exec-argv-extension-none (2)
• sea/test-single-executable-application-inspect-in-sea-flags (2)
• sea/test-single-executable-application-snapshot-and-code-cache (2)
• sea/test-single-executable-application-use-code-cache (2)

Start with reports/2026-06-05.md and the linked CI build range to inspect the failure details behind the progress items. Review the listed infrastructure errors and failing Node.js tests; done means the relevant failure causes have been addressed and the corresponding progress items can be checked.