Nemo157
Nemo157
(The cache also appears to be only partially effective, there were ~280 dependencies built for a PR that doesn't touch the lockfile).
Running with debug logging, I see quite a few duplicate `-sys` crates included in the cache, the cache action only removes files after a week of no access, we may...
Since we are doing infrequent mass dependency updates, I think what we could do is not restore during updates, use that as a sync point to purge the cache and...
I can't see any reasonable way to do it from just our workflow config, opened https://github.com/Swatinem/rust-cache/issues/177
I definitely think it would be nice if we could do something like this. Both the suggestions on how to decide what to include in a site seem easy to...
AFAIK there's no tier metadata published with the targets, is the only place I know we could get this info. It might also be that rustc's tiers don't match the...
Mostly a draft because I want more discussion on the idea, this would _drastically_ reduce the total amount of time crates can consume, from 5.5 hours (15 minutes per build,...
One other case this potentially impacts a lot is when a crate is published with an incorrect lockfile, to get any docs the failure with the old lockfile and then...
> For example, do we try a broken lockfile for each target? Nope, only on the default target, when the default target succeeds we do all the extra-targets with whichever...