CI Reliability 2024-11-30

Failures in node-test-pull-request/63697 to node-test-pull-request/63794 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-11-30.md)

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

Progress

• sequential/test-http-server-request-timeouts-mixed (11)
• parallel/test-file-write-stream4 (5)
• parallel/test-net-write-fully-async-buffer (5)
• parallel/test-watch-file-shared-dependency (5)
• parallel/test-stream-readable-unpipe-resume (4)
• sequential/test-tls-session-timeout (3)
• es-module/test-esm-loader-entry-url (2)
• parallel/test-buffer-tostring-rangeerror (2)
• parallel/test-esm-loader-hooks-inspect-brk (2)
• parallel/test-http-response-status-message (2)
• parallel/test-runner-run (2)
• parallel/test-watch-mode-files_watcher (2)
• parallel/test-without-async-context-frame (2)
• wpt/test-compression (2)
• Backing channel 'JNLP4-connect connection from ... is disconnected. (3)
• Build timed out (after 60 minutes). Marking the build as failed. (2)
• ERROR: Error fetching remote repo 'origin' (5)
• fatal: No rebase in progress? (5)
• Error: - process terminated with status 1, expected 0 (3)
• ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
• fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository (2)

Read reports/2024-11-30.md and inspect the linked node-test-pull-request runs, starting with the failures listed under Progress. Use the named test cases and CI errors to trace the repeated failures. Done means the reported recurring failures are addressed and subsequent CI runs no longer reproduce them.