CI Reliability 2026-07-03

Failures in node-test-pull-request/74426 to node-test-pull-request/74524 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-07-03.md)

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

Progress

• parallel/test-npm-install (15)
• parallel/test-path-win32-normalize-device-names (11)
• parallel/test-debugger-probe-failure-process-exit (5)
• sea/test-single-executable-application (5)
• sea/test-single-executable-application-empty (5)
• test-runner/test-run-watch-cwd-isolation-none-argv (5)
• parallel/test-runner-cli (4)
• parallel/test-runner-flag-propagation (4)
• parallel/test-runner-global-setup-teardown (4)
• parallel/test-debugger-probe-expression-throws (3)
• parallel/test-esm-loader-hooks-inspect-wait (3)
• sequential/test-watch-mode-restart-esm-loading-error (3)
• es-module/test-require-module-tla-print-execution (2)
• parallel/test-debugger-probe-bound-never-hit (2)
• parallel/test-debugger-probe-max-hit-partial (2)
• parallel/test-runner-cli-randomize (2)
• pummel/test-timers (2)
• sequential/test-watch-mode-worker (2)
• wasi/test-wasi-pthread (2)
• ERROR: Error fetching remote repo 'origin' (10)
• ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (4)
• ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (3)
• ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ... (2)
• Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified. (2)
• Failed to trigger node-test-commit (2)

Start with reports/2026-07-03.md and the linked node-test-pull-request builds to inspect the failure details. Work through the unchecked test and CI-error entries, identifying the relevant failure evidence for each item. Done means the listed recurring failures have been addressed and the CI reliability report no longer records them as unresolved.