CI Reliability 2026-06-28

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

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

Progress

• ERROR: Error fetching remote repo 'origin' (6)
• ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (3)
• Unexpected token '<', " (3)
• 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)

Start with reports/2026-06-28.md and the linked node-test-pull-request Jenkins runs, then group the listed failures by cause. Check the affected test names and CI errors first; the work is done when the reported failures are diagnosed and the relevant CI jobs return reliably without introducing new failures.