cargo-bisect-rustc
cargo-bisect-rustc copied to clipboard
leverage existing rustup nightlies
We could avoid network traffic (which to me seems like the big bottleneck, at least when one isn't using the --preserve flag to cargo-bisect-rustc) by looking at what nightlies the user has already installed via rustup, and first testing them before exploring versions that we would have to download from the CI service.
As a historical note, most of my initial development was on good networks (~20-30 MB/s from AWS) so I never worried too much about this, but I agree that it's something we should do.
(I'm getting on the order of 6-7 MB/s at home. That's slow enough here to be annoying, especially when I forget to use --preserve...)
I think this is a good idea. I live in Chile, and internet speed can be pretty sketchy here at times. I feel that this would be a nice-to-have :)