Sergey "Shnatsel" Davidoff
Sergey "Shnatsel" Davidoff
This is fixed as of v0.18-rc2
These tests are executed sequentially using a `Mutex`, so the reported execution time of the tests is inflated. The longest reported test reports the execution time for the entire test...
Also the folder is not shared between regular tests and binary scanning tests. That's also something that can be improved, besides caching it.
Just using the default DB location should help, actually.
Actually it's much simpler than that: the caching seems to be broken, and most of the time is spent compiling the code. https://github.com/rustsec/rustsec/actions/runs/4485191049/jobs/7886488822?pr=835#step:12:2
#839 shaves 5 minutes off the CI time, but caching is still broken.
We've gotten CI times under control. They are 1-2 minutes now. Closing.
The `links` field in Cargo.toml may be of use here, at least as a starting point.
Yes, it seems this is an issue on the Zig side - it doesn't recognize the `--undefined` argument at all, which we [need](https://github.com/rust-secure-code/cargo-auditable/blob/83713a1c609b28d93660c64b8974b0226fe2c7a4/cargo-auditable/src/rustc_wrapper.rs#L60) to reliably inject audit data and make...
Actually we track `nightly` because Rust documentation does. The `platforms` crate is auto-generated, and some of the inputs for it are in the documentation, so we have no choice but...