CI Reliability 2025-01-23

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

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

Progress

• 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)
• parallel/test-http2-invalid-last-stream-id (4)
• sequential/test-worker-prof (4)
• parallel/test-abortsignal-drop-settled-signals (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-net-write-fully-async-hex-string (2)
• parallel/test-permission-dc-worker-threads (2)
• parallel/test-permission-fs-read (2)
• parallel/test-permission-fs-write (2)
• parallel/test-runner-module-mocking (2)
• parallel/test-without-async-context-frame (2)
• sequential/test-http-server-request-timeouts-mixed (2)
• sequential/test-perf-hooks (2)

Start with reports/2025-01-23.md and the linked node-test-pull-request CI runs covering builds 64529 through 64607. Investigate the repeated failures listed under Progress, including missing JUnit reports, Windows EBUSY errors, and named Node.js tests. Done means the relevant recurring CI failures have identified fixes and the affected pull requests no longer fail for those reasons.