CI Reliability 2026-03-19

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

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

Progress

• parallel/test-esm-loader-hooks-inspect-wait (12)
• parallel/test-npm-install (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 (5)
• test-runner/test-run-watch-without-file (4)
• client-proxy/test-http-proxy-request-invalid-char-in-url (2)
• parallel/test-child-process-advanced-serialization-splitted-length-field (2)
• parallel/test-child-process-constructor (2)
• parallel/test-http2-dont-lose-data (2)
• test-runner/test-run-watch-repeatedly (2)
• test-runner/test-run-watch-run-duration (2)
• Error: - process terminated with status 1, expected 0 (13)
• fatal: No rebase in progress? (3)
• ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
• Error: 'utf-8' codec can't decode byte 0xa6 in position 245: invalid start byte (2)
• Failed to trigger node-test-commit (2)

Start with reports/2026-03-19.md and the linked node-test-pull-request runs, then use the listed failing test names and error messages to group the recurring failures. The ncu-ci walk pr --stats=true --markdown reports/2026-03-19.md command shows how the report was generated. Done means the recurring failures are investigated and the corresponding progress entries can be checked off.