-
Notifications
You must be signed in to change notification settings - Fork 1.9k
CI: try free up space in Rust / cargo test (amd64) action
#18709
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
Conversation
|
Oh not sure it (jlumbroso/free-disk-space) works if the action runs in a container 🤔 |
jlumbroso/free-disk-space in CI setup-builder stepRust / cargo test (amd64) action
|
Taking inspiration from examples: datafusion/.github/workflows/rust.yml Lines 365 to 377 in 1dddf03
Which usually cleans about 5gb: But also adding what was suggested here: jlumbroso/free-disk-space#21 Combine together, seems to clean 24gb: 🤯 |
2010YOUY01
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the fix!
I suggest we merge it after CI passes, many recent PRs failed CI due to this reason.
Thanks, looks like there's been 3 consecutively successful runs so the fix seems to work. |
…8709) Closes apache#18692 (hopefully) Trying to get CI to pass consistently, try various techniques.
…8709) Closes apache#18692 (hopefully) Trying to get CI to pass consistently, try various techniques.
…8709) Closes apache#18692 (hopefully) Trying to get CI to pass consistently, try various techniques.
…8709) Closes apache#18692 (hopefully) Trying to get CI to pass consistently, try various techniques.
…on (#18709) (#19037) ## Which issue does this PR close? - part of #18843 - Backports #18709 from @Jefffrey ## Rationale for this change @tobixdev is hitting a CI failure due to out of space on a different PR: - #19017 (comment) @Jefffrey fixed this on main with - #18709 So let's backport that change to branch-51 ## What changes are included in this PR? - Backport #18709 to branch-51 ## Are these changes tested? by ci <!-- We typically require tests for all PRs in order to: 1. Prevent the code from being accidentally broken by subsequent changes 2. Serve as another way to document the expected behavior of the code If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? --> ## Are there any user-facing changes? no Co-authored-by: Jeffrey Vo <jeffrey.vo.australia@gmail.com>
…8709) Closes apache#18692 (hopefully) Trying to get CI to pass consistently, try various techniques.
…8709) Closes apache#18692 (hopefully) Trying to get CI to pass consistently, try various techniques.
…8709) Closes apache#18692 (hopefully) Trying to get CI to pass consistently, try various techniques.
Closes #18692 (hopefully)
Trying to get CI to pass consistently, try various techniques.