Problem
When running the test check_updates_some, and therefore likely others which test these code pathways, the internet is accessed in order to check for rustup updates.
Likely this is missing a RUSTUP_UPDATE_ROOT or similar in the environment during the running of those tests since normally we force --no-self-update etc. on appropriate CLI calls.
Steps
- turn off your wifi/internet connection
cargo test --test cli-exact -- check_updates_some- see if it goes badly, and if so, deal with the fix.
Possible Solution(s)
Likely we simply need to either add a --no-self-update type argument to rustup check or else we need to correctly set up a RUSTUP_UPDATE_ROOT or whatever environment variable is missing.
Problem
When running the test
check_updates_some, and therefore likely others which test these code pathways, the internet is accessed in order to check forrustupupdates.Likely this is missing a
RUSTUP_UPDATE_ROOTor similar in the environment during the running of those tests since normally we force--no-self-updateetc. on appropriate CLI calls.Steps
cargo test --test cli-exact -- check_updates_somePossible Solution(s)
Likely we simply need to either add a
--no-self-updatetype argument torustup checkor else we need to correctly set up aRUSTUP_UPDATE_ROOTor whatever environment variable is missing.