search

fishfolk / bones

An easy-to-use game engine for making real games.
https://fishfolk.org/development/bones/introduction/
Other
221 stars 20 forks source link

CI: Large cache will cause runner to run out of space #480

Open MaxCWhitehead opened 14 hours ago

MaxCWhitehead commented 14 hours ago

First saw some of this and discussed on https://github.com/fishfolk/bones/pull/469 -

This job just failed due to a large cache being unzipped running out of space on actions runner. https://github.com/fishfolk/bones/actions/runs/11241667423/job/31253700224

While the job seems to just abruptly terminate, at the top there is a hidden "Annotions 1 error" drop down, which shows:

System.IO.IOException: No space left on device : '/home/runner/runners/2.320.0/_diag/Worker_20241008-184020-utc.log'

Perhaps we are caching too much or caching too widely across different CI jobs (maybe some do not overlap in build artifacts as much as we think?) - maybe should look at other large rust projects and see how they approach caching.

CC: @nelson137 @zicklag

MaxCWhitehead commented 13 hours ago

We could look into: https://github.com/Swatinem/rust-cache but might take a bit of doing to figure out best configuration.

zicklag commented 13 hours ago

I wonder if maybe we're caching between two jobs that use different versions of Rust. Like we're building the project with nightly, and then with stable or something and using the same cache.