Uh oh!
There was an error while loading. Please reload this page.
[branch-50] chore: Fix no space left on device - #18141
Conversation
no space left on deviceno space left on devicealamb
commented
Oct 17, 2025
Thanks @comphead I took the liberty of pushing a commit to remove calling |
alamb
commented
Oct 17, 2025
Note this PR also updates the |
alamb
commented
Oct 17, 2025
I am going to see if I can find some other consumers of space via #18143 |
comphead
commented
Oct 17, 2025
Great, yep, having just 1 pipeline is time efficient |
alamb
commented
Oct 17, 2025
Here is some findings (as you say we can probably delete PyPy, Python, Go, Ruby and the CodeQL and get back several GB |
comphead
commented
Oct 17, 2025
@alamb looks like this go to go, WDYT should we also backport it to main to avoid such failures for other releases? |
Uh oh!
There was an error while loading. Please reload this page.
## 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 `Closesapache#123` indicates that this PR will close issue apache#123. --> - Closesapache#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 <andrew@nerdnetworks.org>
## 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 <comphead@users.noreply.github.com>
) ## Which issue does this PR close? - related to apache#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 apache#18141 to main ## Are these changes tested? It is part of CI ## Are there any user-facing changes? No Co-authored-by: Oleks V <comphead@users.noreply.github.com>
) ## Which issue does this PR close? - related to apache#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 apache#18141 to main ## Are these changes tested? It is part of CI ## Are there any user-facing changes? No Co-authored-by: Oleks V <comphead@users.noreply.github.com>
) ## Which issue does this PR close? - related to apache#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 apache#18141 to main ## Are these changes tested? It is part of CI ## Are there any user-facing changes? No Co-authored-by: Oleks V <comphead@users.noreply.github.com>
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?