CI Reliability 2026-04-06

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

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

Progress

• Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
• fatal: No rebase in progress? (4)
• Failed to trigger sub builds (3)
• sh: line 12: [: -gt: unary operator expected (3)
• ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
• ERROR: out of memory (2)
• Failed to trigger node-test-commit (2)
• error: remote GitHub already exists. (2)
• sh: line 1: 429:: command not found (2)
• wpt/test-wasm-jsapi (6)
• sequential/test-debugger-pid (3)
• parallel/test-fs-watch-recursive-delete (2)
• parallel/test-http2-client-rststream-before-connect (2)
• parallel/test-http2-close-while-writing (2)
• parallel/test-http2-server-push-stream (2)
• test-runner/test-run-watch-repeatedly (2)
• wpt/test-hr-time (2)
• wpt/test-streams (2)

Start with reports/2026-04-06.md and the linked node-test-pull-request jobs 72400–72498; the report was generated with ncu-ci walk pr --stats=true --markdown. Group the repeated infrastructure and test failures, then use the listed Progress items to track work; done means the identified failures are resolved and the CI failure rate improves.