Do a crater run

[bjorn3]

This will help catching miscompilations and compilation errors. Unfortunately doing a local crater run will probably take several weeks on my system if I would have enough disk space, which I don't. During that time I also likely won't be able to use my system at all.

[m4b]

how much approximate space does a crater run require? is it possible to do a crater run jr? i may/may not be able to help, depending on size and more crucially, network bandwidth requirements

[bjorn3]

how much approximate space does a crater run require?

I have no clue.

is it possible to do a crater run jr?

The test suite of crater has a mini version, but I am pretty sure it is too small to be very useful.

may/may not be able to help, depending on size and more crucially, network bandwidth requirements

Thanks. @pietroalbini how much resources do you estimate a crater run requires?

[pietroalbini]

It currently takes 2.5 days using 60 cores and a couple TBs of storage to run a cargo test run.

[bjorn3]

Thanks! That is way out of reach for me and probably also for @m4b.

[m4b]

@pietroalbini What about network bandwidth ?

@bjorn3 thinking out loud, if jit mode was working that would remove effectively the storage requirement yes ? I would imagine each crate is compiled in memory, and results dumped eg to text file or whatever.

[bjorn3]

In jit mode you still need to store the dependencies. Also the jit mode is not very useful without cargo support as it requires all dependencies to be available in dylib format, which is normally requires you to change the Cargo.toml to set crate-type for each dependency.

[pietroalbini]

@m4b over a day one of our agent (a quarter of the Crater capacity) used an average of 1MB/s with peaks of 50MB/s.