Free more disk space in CI workflows to fix minikube storage failures - #852
Merged
Merged
Conversation
lirenjie95
force-pushed
the
fix/ci-disk-space
branch
3 times, most recently
from
July 27, 2026 12:09
16cfe45 to
71ecaa0
Compare
Contributor
Author
|
Evidence from the Before After ~27 GB freed (previously the same step freed only ~10 GB), giving minikube + full image builds comfortable headroom. The job passed. https://github.com/eclipse-symphony/symphony/actions/runs/30279340656/job/90021422571 |
lirenjie95
force-pushed
the
fix/ci-disk-space
branch
from
July 27, 2026 15:18
71ecaa0 to
2f1fe56
Compare
Haishi2016
approved these changes
Jul 27, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
CI jobs that run minikube plus a full image build keep flaking on disk space:
test (04.workflow-false)on main, 2026-07-23 (original attempt; the run was later re-run and passed): https://github.com/eclipse-symphony/symphony/actions/runs/30039594967/attempts/1buildjob, same error: https://github.com/eclipse-symphony/symphony/actions/runs/26763226111minikube startpulls the kicbase image,mage build:allbuilds all images, andmage cluster:uploads them into minikube — the images end up stored twice under/var/lib/docker. These jobs pass sometimes and flake other times, so the disk headroom is right at the edge.Fix
The
Free up disk spacestep is identical in 5 workflows (integration.yml, go.yml, fault.yml, suite.yml, release.yaml). suite.yml and fault.yml have the same minikube + full image build profile as integration.yml and will hit the same wall eventually; release.yaml builds multi-arch images where a failure becomes a release incident. This PR extends all five copies uniformly, following the standard list from https://github.com/jlumbroso/free-disk-space while keeping the existing hand-writtenrmstyle (no external action):/opt/ghc(~5 GB),/opt/hostedtoolcache/CodeQL(~2-3 GB)/usr/lib/jvm,/opt/microsoft/powershell,/usr/local/lib/node_modules,/usr/local/.ghcup,/opt/hostedtoolcache/Ruby(~0.5-1 GB each)df -h /is printed before and after so the freed amount is visible in the logs./opt/hostedtoolcacheis not removed wholesale since setup-go installs Go there. No workflow in this repo uses CodeQL, setup-java, setup-node, or maven/gradle, so these deletions are safe everywhere.Verification
The before/after
dfoutput from this PR's integration04.workflow-falsejob is posted in a comment below. release.yaml only runs on release so it cannot be exercised here, but its change is identical to the other four files.