CI Reliability 2024-10-16

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

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

Progress

• sequential/test-http-server-request-timeouts-mixed (9)
• parallel/test-file-write-stream4 (7)
• parallel/test-stream-readable-unpipe-resume (4)
• wpt/test-compression (4)
• 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)
• es-module/test-typescript (2)
• parallel/test-http2-large-write-multiple-requests (2)
• parallel/test-net-write-fully-async-buffer (2)
• fatal: No rebase in progress? (6)
• Error: invalid syntax (5)
• ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? (3)
• Failed to trigger sub builds (2)

Start with the linked reliability report for the failures from node-test-pull-request/63031 through 63130, then investigate the listed test names and CI errors. Re-run the affected jobs or tests to identify reproducible failures; done means the recurring failures are fixed and the CI results are green.