By default rusup performs a self-update when installing a new rustc toolchain, Sometimes, the files are locked by windows, and the self update can fail as described here: https://github.com/rust-lang/rustup/issues/2441
Since this is a pipeline run, we have no need to update rustup, and can rely on the version provided by the runner. By disabling the self update, the file conflict The process cannot access the file because it is being used by another process no longer appears as seen in this test PR: https://dev.azure.com/projectmu/mu/_build/results?buildId=65795&view=results
By default
rusupperforms a self-update when installing a new rustc toolchain, Sometimes, the files are locked by windows, and the self update can fail as described here: https://github.com/rust-lang/rustup/issues/2441Since this is a pipeline run, we have no need to update rustup, and can rely on the version provided by the runner. By disabling the self update, the file conflict
The process cannot access the file because it is being used by another processno longer appears as seen in this test PR: https://dev.azure.com/projectmu/mu/_build/results?buildId=65795&view=results