CI Reliability 2026-03-18

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

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

Progress

• parallel/test-npm-install (17)
• parallel/test-esm-loader-hooks-inspect-wait (12)
• sea/test-single-executable-application-assets-raw (12)
• sea/test-single-executable-application-exec-argv (12)
• sea/test-single-executable-application-exec-argv-empty (12)
• sea/test-single-executable-application-snapshot-worker (12)
• parallel/test-debugger-heap-profiler (4)
• sea/test-single-executable-application-assets (4)
• sea/test-single-executable-application-exec-argv-extension-cli (4)
• sea/test-single-executable-application-inspect-in-sea-flags (4)
• test-runner/test-run-watch-without-file (4)
• parallel/test-inspector-network-http (3)
• sequential/test-watch-mode-restart-esm-loading-error (3)
• test-runner/test-output-test-runner-watch-spec (2)
• test-runner/test-run-watch-repeatedly (2)
• test-runner/test-run-watch-run-duration (2)
• wpt/test-web-locks (2)
• Error: - process terminated with status 1, expected 0 (18)
• ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
• Failed to trigger node-test-commit (2)
• fatal: No rebase in progress? (2)

Start with reports/2026-03-18.md, linked from the issue, and inspect the listed failures and their CI runs. Begin with one named test such as parallel/test-npm-install or a sea/test-single-executable-application test, then trace its failure details. Done means the relevant failures are resolved and the corresponding progress items can be checked off.