Skip to content

Conversation

@pan3793
Copy link
Member

@pan3793 pan3793 commented Dec 10, 2025

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Was this patch authored or co-authored using generative AI tooling?

@sarutak
Copy link
Member

sarutak commented Dec 10, 2025

How about just backporting #52545 to branch-3.5 ?
I tried to backport it on my repo and it seems that we can make much free space.

https://github.com/sarutak/spark/actions/runs/20099755653/job/57667392187

Filesystem      Size  Used Avail Use% Mounted on
overlay          73G   62G   12G  85% /
tmpfs            64M     0   64M   0% /dev
shm              64M     0   64M   0% /dev/shm
/dev/root        73G   62G   12G  85% /__e
tmpfs           3.2G  1.2M  3.2G   1% /run/docker.sock
tmpfs           7.9G     0  7.9G   0% /proc/acpi
tmpfs           7.9G     0  7.9G   0% /proc/scsi
tmpfs           7.9G     0  7.9G   0% /sys/firmware

@pan3793
Copy link
Member Author

pan3793 commented Dec 10, 2025

@sarutak, it's even better if it already has a solution, please go ahead to do that to unblock branch-3.5 backport PRs.

@sarutak
Copy link
Member

sarutak commented Dec 10, 2025

@pan3793
OK, I opened a PR (#53427).
Let's see if GA pass by backporting #52545

@pan3793
Copy link
Member Author

pan3793 commented Dec 10, 2025

CI passes, but close this in favor #53427

@pan3793 pan3793 closed this Dec 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants