[branch-50] chore: Fix no space left on device
#18141
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
development-process
alamb
changed the title
no space left on deviceno space left on device
|
Thanks @comphead I took the liberty of pushing a commit to remove calling |
|
Note this PR also updates the |
|
I am going to see if I can find some other consumers of space via #18143 |
Great, yep, having just 1 pipeline is time efficient |
Here is some findings (as you say we can probably delete PyPy, Python, Go, Ruby and the CodeQL and get back several GB |
|
@alamb looks like this go to go, WDYT should we also backport it to main to avoid such failures for other releases? |
alamb
added a commit
to alamb/datafusion
that referenced
this pull request
Oct 18, 2025
## Which issue does this PR close? <!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes apache#123` indicates that this PR will close issue apache#123. --> - Closes apache#18135 ## Rationale for this change <!-- Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed. Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes. --> ## What changes are included in this PR? <!-- There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. --> ## Are these changes tested? <!-- 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? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> <!-- If there are any breaking changes to public APIs, please add the `api change` label. --> --------- Co-authored-by: Andrew Lamb <[email protected]>
This was referenced Oct 18, 2025
github-merge-queue bot
pushed a commit
that referenced
this pull request
Oct 18, 2025
## Which issue does this PR close? - related to #18135 - ## Rationale for this change Our example job was failing due to out of space on other branches, so let's remove some unecessary pre-installed software ## What changes are included in this PR? - forward port changes from #18141 to main ## Are these changes tested? It is part of CI ## Are there any user-facing changes? No Co-authored-by: Oleks V <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Rust / cargo examples (amd64) (pull_request)failing on branch-50 #18135Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?