Recommended ways to slim down ccov builds?

[dpc]

We have a large project, lots of deps, lots of own LoC. Our normal builds product a lot of artifacts already, but ccov ones are huge.

Any recommendations how to retain at least some of the use ccov ability with lower storage use? Would things work e.g. with debug symbols only for local dependencies or something like that?

Generally the problem of debug symbols balooning size of everything Rust-dev related is a common pattern when doing Rust dev tooling and CIs, etc. I can understand and accept why my binary is 120MB unstripped in release build. But why is my target directory 20GB right away is a bit harder for me to internalize. :D

[taiki-e]

Probably the same issue as #335

[dpc]

That seems like one angle, though I don't fully understand it, and we don't have thousands for test binaries.

[taiki-e]

I think what is important in that case is not the number of test binaries, but the number of processes being executed.

I don't know anything about your test, but if you are testing binaries, you would call and test those binaries, right? In that case, each of those calls should be a separate process.

[dpc]

Oh. That's good to know, but I think at the point I was looking at, I didn't even start a single test yet. :D