CI Reliability 2025-02-20

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

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

Progress

• parallel/test-assert-fail (11)
• parallel/test-buffer-tostring-rangeerror (10)
• parallel/test-runner-run-watch (6)
• parallel/test-file-write-stream4 (4)
• parallel/test-http-get-pipeline-problem (3)
• parallel/test-runner-output (3)
• wpt/test-compression (3)
• parallel/test-http-server-connection-list-when-close (2)
• parallel/test-pipe-file-to-http (2)
• sequential/test-tls-session-timeout (2)
• wpt/test-timers (2)
• Build timed out (after 30 minutes). Marking the build as failed. (6)
• ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (6)
• error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] (5)
• fatal: No rebase in progress? (5)
• fatal: detected dubious ownership in repository at 'C:/workspace/node-test-binary-windows-js-suites/build' (4)
• Error: EBUSY: resource busy or locked, rmdir '\\?\c:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.638' (2)

Start with reports/2025-02-20.md and the linked CI jobs to inspect the repeated failures listed in the issue. Use the named test cases and build errors as entry points, then determine which failures remain reproducible. Done means the listed reliability problems have been addressed and the corresponding progress items can be checked off.