Checksum error on nighly in Appveyor

[faern]

I more or less constantly (but randomly) hit the following issue with AppVeyor on nightly: rust-lang/rustup#346

On nightly the checksum check fails with:

rustup-init.exe -y --default-host %TARGET% --default-toolchain %RUST_VERSION%
info: syncing channel updates for 'nightly-x86_64-pc-windows-msvc'
info: update not yet available, sorry! try again later
error: checksum failed, expected: '63c2dd25afc95dcfb4d14dedb6134137bd350df2efde824ca9ac60da16cff216', calculated: 'aaa5fc97776fdbf2fc4aa635f405fd32fb91262b667a1b434f7ad30ca51978ca'
Command exited with code 1

This is of course not to be blamed on trust. But I was thinking that if it's not just me having this issue it might be nice to fix it in trust anyway. If I'm the only one with these problems then ignore this issue.

I made this change to appveyor.yml and that seems to solve the problem. It is not elegant, but it works. Replace the rustup-init part with this:

- ps: >-
      If ($Env:RUST_VERSION -eq 'nightly') {
        Start-FileDownload "https://static.rust-lang.org/dist/rust-${env:RUST_VERSION}-${env:TARGET}.exe"
        cmd /c rust-%RUST_VERSION%-%TARGET%.exe /VERYSILENT /NORESTART /DIR="C:\Program Files (x86)\Rust"
        $Env:PATH += ';C:\Program Files (x86)\Rust\bin'
      } Else {
        cmd /c curl -sSf -o rustup-init.exe https://win.rustup.rs/
        cmd /c rustup-init.exe -y --default-host %TARGET% --default-toolchain %RUST_VERSION%
        $Env:PATH += ';C:\Users\appveyor\.cargo\bin'
      }

It does have the problem that cmd /c rustup-init.exe -y ... will output lots of ugly red output during the build, but it does not fail at least. Any idea how to silence that?

The reason for staying with rustup at all for non-nightly builds is that you can't download the latest stable release form the static.rust-lang.org server without manually specifying the version number you want.

[faern]

As the issues say, this problem is temporary. However, it is annoying. Today the rustup installation works for me. If people are having this problem from time to time, maybe it's still preferred to install nightly in a way that will always work?

[faern]

I have not had this problem for a very long time now. Might still be random, but probably an unlikely error. Closing the issue.