CI Reliability 2026-06-07

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

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

Progress

• ERROR: Error fetching remote repo 'origin' (5)
• Failed to trigger fanned build (9)
• Failed to trigger sub builds (7)
• Error: Timed out waiting for restart (2)
• fatal: No rebase in progress? (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)
• addons/worker-addon-exit/test (2)
• parallel/test-cluster-dgram-reuse (2)
• parallel/test-debugger-probe-failure-process-exit (2)
• parallel/test-http-server-consumed-timeout (2)
• parallel/test-watch-mode-files_watcher (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-07.md and the Jenkins jobs linked in the issue, then review the listed failure categories and affected Node.js tests. The issue has no single entry point or defined fix; completion would require identifying causes for the failures, addressing them, and updating the Progress checklist.