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/63509 to node-test-pull-request/63594 that failed 2 or more PRs (Generated with ncu-ci walk pr --stats=true --markdown reports/2024-11-18.md)
ncu-ci walk pr --stats=true --markdown reports/2024-11-18.md
Open https://github.com/nodejs/reliability/blob/main/reports/2024-11-18.md to see failure details
Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 3575467, exit value: 1
Failed to trigger sub builds
fatal: No rebase in progress?
parallel/test-file-write-stream4
parallel/test-stream-readable-unpipe-resume
sequential/test-http-server-request-timeouts-mixed
parallel/test-cluster-fork-stdio
parallel/test-http-get-pipeline-problem
parallel/test-net-write-fully-async-buffer
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Failures in node-test-pull-request/63509 to node-test-pull-request/63594 that failed 2 or more PRs
(Generated with
ncu-ci walk pr --stats=true --markdown reports/2024-11-18.md)Open https://github.com/nodejs/reliability/blob/main/reports/2024-11-18.md to see failure details
Progress
Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 3575467, exit value: 1(2)Failed to trigger sub builds(8)fatal: No rebase in progress?(2)parallel/test-file-write-stream4(4)parallel/test-stream-readable-unpipe-resume(3)sequential/test-http-server-request-timeouts-mixed(3)parallel/test-cluster-fork-stdio(2)parallel/test-http-get-pipeline-problem(2)parallel/test-net-write-fully-async-buffer(2)The text was updated successfully, but these errors were encountered: