CI Reliability 2026-06-20

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

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

Progress

• Backing channel 'JNLP4-connect connection from ... is disconnected. (4)
• fatal: No rebase in progress? (10)
• ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (5)
• Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified. (4)
• fatal: no rebase in progress (4)
• ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (3)
• addons/worker-addon-exit/test (14)
• benchmark/test-benchmark-v8 (5)
• parallel/test-runner-cli (5)
• parallel/test-runner-coverage (5)
• parallel/test-runner-coverage-default-exclusion (5)
• parallel/test-runner-coverage-isolation-none-api (5)
• parallel/test-runner-coverage-source-map (5)
• parallel/test-runner-coverage-thresholds (5)
• parallel/test-runner-flag-propagation (5)
• parallel/test-runner-run-coverage (5)
• test-runner/test-output-coverage-failure (5)
• test-runner/test-output-coverage-short-filename (5)
• test-runner/test-output-coverage-width-100 (5)
• test-runner/test-output-coverage-width-100-uncovered-lines (5)
• test-runner/test-output-coverage-width-150 (5)
• test-runner/test-output-coverage-width-150-uncovered-lines (5)
• test-runner/test-output-coverage-width-40 (5)
• test-runner/test-output-coverage-width-80 (5)
• test-runner/test-output-coverage-width-80-uncovered-lines (5)
• test-runner/test-output-coverage-width-infinity (5)
• test-runner/test-output-coverage-width-infinity-uncovered-lines (5)
• test-runner/test-output-coverage-with-mock (5)
• test-runner/test-output-coverage-with-mock-cjs (5)
• test-runner/test-output-lcov-reporter (5)
• test-runner/test-output-typescript-coverage (5)
• parallel/test-util-styletext (4)
• sea/test-build-sea (4)
• parallel/test-cluster-dgram-reuse (3)
• parallel/test-debugger-probe-failure-process-exit (3)
• parallel/test-fs-utimes-y2K38 (3)
• parallel/test-runner-watch-mode (3)
• sea/test-build-sea-already-exists (3)
• sea/test-build-sea-custom-argv0 (3)
• sea/test-build-sea-executable-field (3)
• sea/test-single-executable-application-asset-keys (3)
• sea/test-single-executable-application-esm (3)
• sea/test-single-executable-application-exec-argv-extension-cli (3)
• parallel/test-debugger-probe-global-option-order (2)
• parallel/test-heapsnapshot-near-heap-limit-worker (2)
• parallel/test-http-server-consumed-timeout (2)
• parallel/test-http2-close-while-writing (2)
• sea/test-build-sea-missing-output (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-code-cache (2)
• sea/test-single-executable-application-exec-argv (2)
• sea/test-single-executable-application-exec-argv-extension-env (2)
• sea/test-single-executable-application-exec-argv-extension-none (2)
• sea/test-single-executable-application-snapshot-and-code-cache (2)
• wpt/test-streams (2)

Start with reports/2026-06-20.md and the linked node-test-pull-request Jenkins runs to inspect the detailed failure causes behind the listed progress items. Determine which failures are actionable and address them until the reported CI failures are resolved and the affected tests and jobs pass reliably.