CI Reliability 2025-02-07

Failures in node-test-pull-request/64943 to node-test-pull-request/65040 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-02-07.md)

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

Progress

• parallel/test-assert-fail (10)
• parallel/test-runner-run-watch (9)
• parallel/test-file-write-stream4 (6)
• parallel/test-net-write-fully-async-buffer (5)
• es-module/test-esm-loader-entry-url (2)
• parallel/test-child-process-cwd (2)
• parallel/test-node-output-eval (2)
• parallel/test-runner-output (2)
• parallel/test-without-async-context-frame (2)
• parallel/test-zlib-brotli-16GB (2)
• sequential/test-perf-hooks (2)
• sequential/test-performance-eventloopdelay (2)
• sequential/test-tls-session-timeout (2)
• ERROR: Error fetching remote repo 'origin' (3)
• Error: list index out of range (6)
• error: remote GitHub already exists. (3)
• fatal: No rebase in progress? (3)
• ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
• Failed to trigger sub builds (2)

Start with reports/2025-02-07.md and the linked node-test-pull-request Jenkins runs to inspect the listed failures. Review the affected tests and CI errors, then use the Progress checklist to track which failures have been resolved; done means the listed recurring failures are addressed and the checklist reflects that progress.