CI Reliability 2025-01-22

Failures in node-test-pull-request/64498 to node-test-pull-request/64595 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-01-22.md)

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

Progress

• ERROR: Error fetching remote repo 'origin' (3)
• ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (6)
• Error: - process terminated with status 1, expected 0 (2)
• Error: EBUSY: resource busy or locked, rmdir '\\?\C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.638' (2)
• Error: EBUSY: resource busy or locked, rmdir '\\?\c:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.638' (2)
• fatal: Could not read from remote repository. (2)
• fatal: No rebase in progress? (2)
• parallel/test-http2-invalid-last-stream-id (4)
• sequential/test-http-server-request-timeouts-mixed (4)
• sequential/test-worker-prof (4)
• parallel/test-abortsignal-drop-settled-signals (3)
• parallel/test-net-write-fully-async-buffer (3)
• parallel/test-net-write-fully-async-hex-string (3)
• benchmark/test-benchmark-http2 (2)
• node-api/test_threadsafe_function/test (2)
• parallel/test-buffer-tostring-range (2)
• parallel/test-http-get-pipeline-problem (2)
• parallel/test-http2-premature-close (2)
• parallel/test-without-async-context-frame (2)
• sequential/test-perf-hooks (2)

Start with reports/2025-01-22.md and the linked node-test-pull-request builds to inspect the repeated failures listed in the issue. Use the named test entries and CI errors to identify which failures are actionable and verify them against current CI behavior. Done means the selected reliability failures are addressed and the corresponding CI jobs no longer reproduce them.