CI Reliability 2026-06-29

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

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

Progress

• sea/test-single-executable-application-empty (5)
• parallel/test-blob (3)
• test-runner/test-run-watch-cwd-isolation-none-argv (3)
• parallel/test-heapsnapshot-near-heap-limit-by-api-in-worker (2)
• parallel/test-http-server-consumed-timeout (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' (8)
• ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)

Start with reports/2026-06-29.md and the linked node-test-pull-request runs, then inspect the listed failures such as sea/test-single-executable-application-empty and parallel/test-blob. Reproduce the affected CI failures and trace each to its test or infrastructure cause; done means the repeated failures in this report are resolved and the CI runs are green.