CI Reliability 2026-06-30

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

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

Progress

• sea/test-single-executable-application-empty (9)
• parallel/test-path-win32-normalize-device-names (5)
• parallel/test-npm-install (4)
• test-runner/test-run-watch-cwd-isolation-none-argv (4)
• parallel/test-blob (3)
• parallel/test-esm-loader-hooks-inspect-wait (2)
• parallel/test-heapsnapshot-near-heap-limit-by-api-in-worker (2)
• parallel/test-http-server-consumed-timeout (2)
• parallel/test-process-finalization (2)
• parallel/test-sqlite-backup (2)
• parallel/test-web-locks (2)
• sea/test-build-sea-custom-argv0 (2)
• sea/test-single-executable-application-asset-keys (2)
• sea/test-single-executable-application-exec-argv-extension-cli (2)
• sea/test-single-executable-application-inspect (2)
• sea/test-single-executable-application-snapshot (2)
• ERROR: Error fetching remote repo 'origin' (7)
• ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)

Start with reports/2026-06-30.md and the linked CI runs from node-test-pull-request/74344 through 74443. Inspect the repeated failures listed in the Progress checklist, beginning with one test such as sea/test-single-executable-application-empty. Done means the selected recurring failure is addressed and the corresponding CI runs no longer fail.