CI Reliability 2026-06-16

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

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

Progress

• ERROR: Error fetching remote repo 'origin' (6)
• fatal: No rebase in progress? (3)
• ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
• fatal: no rebase in progress (2)
• addons/worker-addon-exit/test (13)
• es-module/test-vm-contextified-script-leak (3)
• parallel/test-debugger-probe-failure-process-exit (3)
• parallel/test-http-server-consumed-timeout (2)
• parallel/test-runner-watch-mode (2)
• parallel/test-util-styletext (2)
• sea/test-build-sea (2)
• sea/test-build-sea-already-exists (2)
• sea/test-build-sea-custom-argv0 (2)
• sea/test-build-sea-executable-field (2)
• sea/test-build-sea-missing-output (2)
• sea/test-single-executable-application-asset-keys (2)
• sea/test-single-executable-application-asset-keys-empty (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-extension-cli (2)

Start with reports/2026-06-16.md and the Jenkins runs from node-test-pull-request/74072 through 74165. Use the listed failure groups and the ncu-ci walk pr --stats=true --markdown command as entry points, then investigate the affected tests and CI errors. Done means the recurring failures are addressed and the affected CI runs become reliable.