CI Reliability 2024-09-30

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

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

Progress

• Build timed out (after 30 minutes). Marking the build as failed. (2)
• ERROR: Error fetching remote repo 'origin' (4)
• Error: invalid syntax (7)
• Error: EBUSY: resource busy or locked, rmdir '\\?\c:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.637' (2)
• fatal: No rebase in progress? (2)
• parallel/test-http-get-pipeline-problem (5)
• parallel/test-http2-large-write-multiple-requests (5)
• parallel/test-cluster-fork-stdio (4)
• parallel/test-stream-readable-unpipe-resume (4)
• es-module/test-loaders-workers-spawned (3)
• parallel/test-async-context-frame (3)
• parallel/test-file-write-stream4 (3)
• parallel/test-net-write-fully-async-buffer (3)
• es-module/test-esm-child-process-fork-main (2)
• parallel/test-child-process-disconnect (2)
• parallel/test-child-process-fork (2)
• parallel/test-child-process-fork-closed-channel-segfault (2)
• parallel/test-child-process-fork-getconnections (2)
• parallel/test-child-process-fork-net (2)
• parallel/test-child-process-fork-net-server (2)
• parallel/test-child-process-fork-net-socket (2)
• parallel/test-child-process-fork-stdio-string-variant (2)
• parallel/test-child-process-http-socket-leak (2)
• parallel/test-child-process-ipc-next-tick (2)
• parallel/test-child-process-send-keep-open (2)
• parallel/test-child-process-send-returns-boolean (2)
• parallel/test-cluster-accept-fail (2)
• parallel/test-cluster-bind-twice (2)
• parallel/test-cluster-concurrent-disconnect (2)
• parallel/test-cluster-disconnect (2)
• parallel/test-cluster-disconnect-unshared-tcp (2)
• parallel/test-cluster-eaccess (2)
• parallel/test-cluster-eaddrinuse (2)
• parallel/test-cluster-invalid-message (2)
• parallel/test-cluster-message (2)
• parallel/test-cluster-net-listen-ipv6only-false (2)
• parallel/test-cluster-net-send (2)
• parallel/test-cluster-primary-error (2)
• parallel/test-cluster-primary-kill (2)
• parallel/test-cluster-rr-handle-close (2)
• parallel/test-cluster-rr-handle-keep-loop-alive (2)
• parallel/test-cluster-rr-handle-ref-unref (2)
• parallel/test-cluster-send-deadlock (2)
• parallel/test-cluster-send-handle-twice (2)
• parallel/test-cluster-server-restart-none (2)
• parallel/test-cluster-server-restart-rr (2)
• parallel/test-cluster-shared-leak (2)
• parallel/test-cluster-worker-disconnect-on-error (2)
• parallel/test-cluster-worker-handle-close (2)
• parallel/test-cluster-worker-no-exit (2)
• parallel/test-cluster-worker-wait-server-close (2)
• parallel/test-dgram-exclusive-implicit-bind (2)
• parallel/test-fs-rmdir-recursive-sync-warns-on-file (2)
• parallel/test-fs-rmdir-recursive-throws-on-file (2)
• parallel/test-fs-rmdir-recursive-warns-on-file (2)
• parallel/test-inspector-connect-to-main-thread (2)
• parallel/test-inspector-open (2)
• parallel/test-net-child-process-connect-reset (2)
• parallel/test-net-listen-exclusive-random-ports (2)
• parallel/test-net-listen-twice (2)
• parallel/test-net-server-close-before-ipc-response (2)
• parallel/test-runner-output (2)
• parallel/test-stdout-close-catch (2)
• parallel/test-tls-ticket-cluster (2)
• sequential/test-child-process-pass-fd (2)
• sequential/test-cluster-net-listen-ipv6only-none (2)
• sequential/test-cluster-net-listen-ipv6only-rr (2)
• sequential/test-cluster-send-handle-large-payload (2)
• sequential/test-inspector-open-dispose (2)
• sequential/test-net-listen-shared-ports (2)

Start with reports/2024-09-30.md and the linked node-test-pull-request jobs, then review the listed test and infrastructure failures. Group the recurring failures by cause and verify them against the affected CI runs. Done means the reported recurring failures have identified fixes and no longer reproduce in CI.