We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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)
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
Build timed out (after 30 minutes). Marking the build as failed.
ERROR: Error fetching remote repo 'origin'
Error: invalid syntax
Error: EBUSY: resource busy or locked, rmdir '\\?\c:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.637'
fatal: No rebase in progress?
parallel/test-http-get-pipeline-problem
parallel/test-http2-large-write-multiple-requests
parallel/test-cluster-fork-stdio
parallel/test-stream-readable-unpipe-resume
es-module/test-loaders-workers-spawned
parallel/test-async-context-frame
parallel/test-file-write-stream4
parallel/test-net-write-fully-async-buffer
es-module/test-esm-child-process-fork-main
parallel/test-child-process-disconnect
parallel/test-child-process-fork
parallel/test-child-process-fork-closed-channel-segfault
parallel/test-child-process-fork-getconnections
parallel/test-child-process-fork-net
parallel/test-child-process-fork-net-server
parallel/test-child-process-fork-net-socket
parallel/test-child-process-fork-stdio-string-variant
parallel/test-child-process-http-socket-leak
parallel/test-child-process-ipc-next-tick
parallel/test-child-process-send-keep-open
parallel/test-child-process-send-returns-boolean
parallel/test-cluster-accept-fail
parallel/test-cluster-bind-twice
parallel/test-cluster-concurrent-disconnect
parallel/test-cluster-disconnect
parallel/test-cluster-disconnect-unshared-tcp
parallel/test-cluster-eaccess
parallel/test-cluster-eaddrinuse
parallel/test-cluster-invalid-message
parallel/test-cluster-message
parallel/test-cluster-net-listen-ipv6only-false
parallel/test-cluster-net-send
parallel/test-cluster-primary-error
parallel/test-cluster-primary-kill
parallel/test-cluster-rr-handle-close
parallel/test-cluster-rr-handle-keep-loop-alive
parallel/test-cluster-rr-handle-ref-unref
parallel/test-cluster-send-deadlock
parallel/test-cluster-send-handle-twice
parallel/test-cluster-server-restart-none
parallel/test-cluster-server-restart-rr
parallel/test-cluster-shared-leak
parallel/test-cluster-worker-disconnect-on-error
parallel/test-cluster-worker-handle-close
parallel/test-cluster-worker-no-exit
parallel/test-cluster-worker-wait-server-close
parallel/test-dgram-exclusive-implicit-bind
parallel/test-fs-rmdir-recursive-sync-warns-on-file
parallel/test-fs-rmdir-recursive-throws-on-file
parallel/test-fs-rmdir-recursive-warns-on-file
parallel/test-inspector-connect-to-main-thread
parallel/test-inspector-open
parallel/test-net-child-process-connect-reset
parallel/test-net-listen-exclusive-random-ports
parallel/test-net-listen-twice
parallel/test-net-server-close-before-ipc-response
parallel/test-runner-output
parallel/test-stdout-close-catch
parallel/test-tls-ticket-cluster
sequential/test-child-process-pass-fd
sequential/test-cluster-net-listen-ipv6only-none
sequential/test-cluster-net-listen-ipv6only-rr
sequential/test-cluster-send-handle-large-payload
sequential/test-inspector-open-dispose
sequential/test-net-listen-shared-ports
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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)The text was updated successfully, but these errors were encountered: