fix: integration / Archery test With other arrows container ran out of space#9043
fix: integration / Archery test With other arrows container ran out of space#9043Jefffrey merged 2 commits intoapache:mainfrom
Conversation
Signed-off-by: lyang24 <[email protected]>
|
the problem is fs container's fs is full before the cp -a command after js build. the easiest way out is spend more money on a larger machine :( let me look into some disk optimizations opportunities === BEFORE CP: Memory and Disk === |
|
I know in DataFusion we run into similar disk space usage issues often and one fix was to manually remove unneeded software: But given the image for integration tests is custom and from arrow, not sure how effective it might be 🤔 |
f991723 to
6c5e377
Compare
Yes i think that should be the approach here as well. After investigating further the runner container is polluted starting with 63gb/72gb before the checkout step. |
aaa0b8d to
4d53b77
Compare
save disk: host clean up and git shallow clone. Signed-off-by: lyang24 <[email protected]>
4d53b77 to
af1354e
Compare
was able to get enough space after mimic data fusion by adding a clean up to delete unneed software |
Jefffrey
left a comment
There was a problem hiding this comment.
Great work debugging this 🎉
|
Thanks @lyang24 |
Which issue does this PR close?
integration / Archery test With other arrows (push)CI check failing on main #9024.Rationale for this change
the ci container starts with 63gb / 72gb used, the 9GB remaining disk space is barely enough for a cross build in 7 languages that leads to ci being stuck.
this is what a debug step after initialize container shows
=== CONTAINER DISK USAGE ===
Filesystem Size Used Avail Use% Mounted on
overlay 72G 63G 9.5G 87% /
What changes are included in this PR?
=== Cleaning up host disk space ===
Disk space before cleanup:
Filesystem Size Used Avail Use% Mounted on
overlay 72G 63G 9.5G 87% /
Disk space after cleanup:
Filesystem Size Used Avail Use% Mounted on
overlay 72G 57G 16G 79% /
optimization results we have 6.1 GB left after build
=== After Build ===
Filesystem Size Used Avail Use% Mounted on
overlay 72G 66G 6.1G 92% /
Are these changes tested?
tested by github ci
Are there any user-facing changes?
no