CI Reliability 2026-01-24

Failures in node-test-pull-request/70894 to node-test-pull-request/70988 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-24.md)

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

Progress

• parallel/test-repl-programmatic-history (16)
• parallel/test-inspector-network-http2-compressed (9)
• sequential/test-watch-mode-restart-esm-loading-error (4)
• node-api/test_threadsafe_function/test (3)
• parallel/test-http2-close-while-writing (3)
• parallel/test-zlib-brotli-16GB (3)
• test-runner/test-run-watch-repeatedly (3)
• parallel/test-fs-watch-recursive-delete (2)
• parallel/test-http-request-host-header (2)
• parallel/test-quic-test-client (2)
• parallel/test-timers-immediate-queue (2)
• pummel/test-repl-paste-big-data (2)
• sea/test-build-sea (2)
• sea/test-build-sea-executable-field (2)
• sequential/test-performance-eventloopdelay (2)
• test-runner/test-run-watch-dependency-repeatedly (2)
• wpt/test-hr-time (2)
• wpt/test-streams (2)
• ERROR: Error fetching remote repo 'origin' (2)
• Failed to trigger node-test-commit (2)

Start with reports/2026-01-24.md and the linked CI jobs, then reproduce the listed failures such as parallel/test-repl-programmatic-history and sequential/test-watch-mode-restart-esm-loading-error. Review each unchecked test or infrastructure error and use its CI output to determine the relevant area. Done means the failures have been addressed and the corresponding progress entries can be checked.