-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
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
CI Reliability 2024-07-16 #922
Comments
nodejs-github-bot
pushed a commit
to nodejs/node
that referenced
this issue
Jul 22, 2024
In debug builds, the node binary could exceed 2GB and can not be read by postject. PR-URL: #53918 Refs: nodejs/reliability#922 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
targos
pushed a commit
to nodejs/node
that referenced
this issue
Jul 28, 2024
In debug builds, the node binary could exceed 2GB and can not be read by postject. PR-URL: #53918 Refs: nodejs/reliability#922 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
RafaelGSS
pushed a commit
to nodejs/node
that referenced
this issue
Aug 5, 2024
In debug builds, the node binary could exceed 2GB and can not be read by postject. PR-URL: #53918 Refs: nodejs/reliability#922 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
marco-ippolito
pushed a commit
to nodejs/node
that referenced
this issue
Aug 19, 2024
In debug builds, the node binary could exceed 2GB and can not be read by postject. PR-URL: #53918 Refs: nodejs/reliability#922 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
marco-ippolito
pushed a commit
to nodejs/node
that referenced
this issue
Aug 19, 2024
In debug builds, the node binary could exceed 2GB and can not be read by postject. PR-URL: #53918 Refs: nodejs/reliability#922 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
marco-ippolito
pushed a commit
to nodejs/node
that referenced
this issue
Aug 19, 2024
In debug builds, the node binary could exceed 2GB and can not be read by postject. PR-URL: #53918 Refs: nodejs/reliability#922 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Failures in node-test-pull-request/60248 to node-test-pull-request/60341 that failed 2 or more PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md
)Git Failure
Build Failure
fatal: No rebase in progress?
Example
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Example
JSTest Failure
parallel/test-net-write-fully-async-buffer
Example
sequential/test-http-server-request-timeouts-mixed
Example
parallel/test-dns
Example
wpt/test-compression
Example
parallel/test-file-write-stream4
Example
parallel/test-fs-watch-recursive-delete
Example
parallel/test-performance-function
Example
parallel/test-sqlite
Example
pummel/test-hash-seed
Example
sequential/test-single-executable-application-empty
Example
Progress
fatal: No rebase in progress?
(6)ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
(2)parallel/test-net-write-fully-async-buffer
(8)sequential/test-http-server-request-timeouts-mixed
(8)parallel/test-dns
(6)wpt/test-compression
(3)parallel/test-file-write-stream4
(2)parallel/test-fs-watch-recursive-delete
(2)parallel/test-performance-function
(2)parallel/test-sqlite
(2)pummel/test-hash-seed
(2)sequential/test-single-executable-application-empty
(2)The text was updated successfully, but these errors were encountered: