@Robert @Will Jones I have been fighting with GitHub actions and this periodic issue we see on link

= note: /usr/bin/ld: final link failed: No space left on device

I don't know why this keeps happening, I nuked all our caches in Actions, but it still shows up 😞 I'm only seeing it on Linux but also experience it locally. This seems like a difficult to reproduce bug in Cargo unfortunately. I'm still trying to figure out what the heck is going on here, but if your travels have pointed out anything interesting, please let me know

Just a random thought: might be good to check if we have more duplicate dependencies right now, which might be taking up more space

I am periodically running

cargo +nightly udeps

fwiw

Hey @rtyler, in case removing duplicate dependencies also doesn't help, you can probably try these as well: • Disable incremental compilation in Cargo (config property here) - Incremental compilation caches additional info to disk during compilation to speed up builds. Disabling it might help save disk space, but we may need to check it's implications on compilation time. • Add this Github Action called free-disk-space which is configurable and frees disk space on Ubuntu based runners.

I actually enabled incremental compilation earlier this week and it unfortunately didn't help 😕

Is it possible to try disabling incremental compilation? And yes you're right, something looks to be happening during the test runs, I just tried compiling and running tests on an Ubuntu instance and the

target

folder is showing up as 7.3GB 😅

@Omkar in CI CARGO_INCREMENTAL=0 is set already 😕

Ohh got it okay, I'll check further and get back

That's large, but what is the size if you set

RUSTFLAGS: "-C debuginfo=1"

(which we do in CI)

i suspect that this at least has something to do with the sheer number of integration tests we're using, since each of those must be fully linked binaries. On my local machine when testing, the integration test binaries are each over 700M

Yeah we should consolidate those into single binaries

I also seem to remember thinking that some of these could / should live in the crate itself ..

@Will Jones RUSTFLAGS does chomp down to 3.3GB 😛 Each of these test binaries are now only 4-500MB!

Thanks @rtyler, I just tried your PR. The tests worked like a charm, dropped a comment here. Cheers!

I added a

Cargo.toml

change to make development easier as well. Once this is merged I think there will be a lot more that will be unblocked 🤞

My

delta-rs

workspace was 30 GB of rust compile targets 🤯