CI Reliability 2026-02-08

Failures in node-test-pull-request/71136 to node-test-pull-request/71232 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-02-08.md)

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

Progress

• parallel/test-repl-programmatic-history (12)
• sequential/test-watch-mode-restart-esm-loading-error (6)
• parallel/test-http2-close-while-writing (4)
• sequential/test-performance-eventloopdelay (4)
• parallel/test-node-output-sourcemaps (3)
• sequential/test-single-executable-application-empty (3)
• wpt/test-hr-time (3)
• async-hooks/test-emit-before-on-destroyed (2)
• parallel/test-child-process-fork-exec-path (2)
• parallel/test-crypto-dh-generate-keys (2)
• parallel/test-file-write-stream4 (2)
• parallel/test-http-client-response-domain (2)
• parallel/test-module-loading-globalpaths (2)
• parallel/test-promise-reject-callback-exception (2)
• parallel/test-runner-output (2)
• parallel/test-runner-watch-mode (2)
• parallel/test-zlib-brotli-16GB (2)
• test-runner/test-run-watch-emit-restarted (2)
• Build timed out (after 60 minutes). Marking the build as failed. (2)
• Failed to trigger sub builds (3)
• fatal: No rebase in progress? (3)
• error: remote GitHub already exists. (2)

Start with reports/2026-02-08.md and the linked CI runs from node-test-pull-request/71136 through 71232. Investigate the listed failures, beginning with the highest-count tests such as parallel/test-repl-programmatic-history and sequential/test-watch-mode-restart-esm-loading-error. Done means the listed reliability failures are addressed and the progress items can be checked off.