CI Reliability 2024-10-17

Failures in node-test-pull-request/63052 to node-test-pull-request/63148 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-10-17.md)

Open https://github.com/nodejs/reliability/blob/main/reports/2024-10-17.md to see failure details

Progress

• sequential/test-http-server-request-timeouts-mixed (11)
• parallel/test-file-write-stream4 (7)
• parallel/test-stream-readable-unpipe-resume (5)
• parallel/test-fs-promises-watch (3)
• parallel/test-fs-watch (3)
• parallel/test-fs-watch-recursive-delete (3)
• parallel/test-watch-mode-files_watcher (3)
• pummel/test-fs-watch-non-recursive (3)
• sequential/test-fs-watch (3)
• wpt/test-compression (3)
• parallel/test-http2-large-write-multiple-requests (2)
• parallel/test-runner-output (2)
• pummel/test-timers (2)
• Error: invalid syntax (6)
• fatal: No rebase in progress? (6)
• ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (4)
• Failed to trigger sub builds (2)

Start with the linked reliability report at reports/2024-10-17.md and review the listed failing tests, including test-http-server-request-timeouts-mixed and the fs-watch cases. Use the ncu-ci walk pr command context to trace the failures across the referenced CI builds. Done means the reported recurring failures have been investigated and the affected CI runs are reliable again.