CI Reliability 2025-02-19

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

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

Progress

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

Start with reports/2025-02-19.md and the linked node-test-pull-request runs, using the listed failure names to trace recurring CI problems. Review the ncu-ci walk pr --stats=true --markdown reports/2025-02-19.md output and investigate the unchecked failures. Done means the reported recurring failures are addressed and the affected CI runs no longer reproduce them.