Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
rustup
has a mechanism for self-updating, which triggers whenever you request it to install a new toolchain. This is annoying to have happen in CI though, since it increases build time for no benefit (both the check itself, and the eventual update if rustup deems it necessary).So let's disable this!
Since this is a behavioural change, it could be considered a breaking change, though I will argue that it isn't, people shouldn't need to update
rustup
itself during a build (rustup update
to fetch a newerrustc
/cargo
still works fine).Related issue:
#246, the proposed workaround in there (
--no-self-update
) wouldn't be necessary any more.Check list