CI Reliability 2026-01-14

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

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

Progress

• parallel/test-repl-programmatic-history (10)
• node-api/test_threadsafe_function/test (9)
• es-module/test-esm-loader-hooks (6)
• es-module/test-esm-detect-ambiguous (5)
• es-module/test-esm-loader-programmatically (5)
• es-module/test-esm-loader-spawn-promisified (5)
• parallel/test-quic-test-client (5)
• es-module/test-esm-initialization (4)
• es-module/test-esm-loader (4)
• es-module/test-esm-loader-side-effect (4)
• es-module/test-esm-preserve-symlinks-not-found (4)
• es-module/test-esm-preserve-symlinks-not-found-plain (4)
• test-runner/test-run-watch-cwd-isolation-none (4)
• sequential/test-performance-eventloopdelay (3)
• async-hooks/test-improper-order (2)
• client-proxy/test-https-proxy-request-invalid-char-in-url (2)
• parallel/test-buffer-slow (2)
• parallel/test-crypto-cipheriv-decipheriv (2)
• parallel/test-http2-close-while-writing (2)
• test-runner/test-run-watch-repeatedly (2)
• wpt/test-wasm-webapi (2)
• Build timed out (after 30 minutes). Marking the build as failed. (3)
• ERROR: Error fetching remote repo 'origin' (5)
• ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
• Failed to trigger node-test-commit (2)
• fatal: No rebase in progress? (2)

Start with reports/2026-01-14.md and the linked CI job range to inspect the failure details, then examine the listed failing tests and infrastructure errors. The work is complete when the reported recurring failures are investigated and the affected CI runs are reliable again.