CI Reliability 2026-04-05

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

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

Progress

• Backing channel 'JNLP4-connect connection from ... is disconnected. (2)
• ERROR: out of memory (3)
• Failed to trigger node-test-commit (3)
• Failed to trigger sub builds (3)
• error: remote GitHub already exists. (3)
• fatal: No rebase in progress? (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)
• Unexpected token '<', " (3)
• wpt/test-wasm-jsapi (5)
• 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)
• parallel/test-inspector-exit-worker-in-wait-for-connection (2)
• parallel/test-net-socket-reset-send (2)
• wpt/test-streams (2)

Start with reports/2026-04-05.md and the linked node-test-pull-request Jenkins runs to inspect the listed failure details. Trace each recurring failure to its source and verify that the affected CI jobs or tests no longer fail; the issue provides no specific source files or test entry point.