Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

appveyor: Use VS2017 for all our images #58854

Merged
merged 2 commits into from
Mar 16, 2019
Merged

appveyor: Use VS2017 for all our images #58854

merged 2 commits into from
Mar 16, 2019

Commits on Mar 1, 2019

  1. Add back in MSVC version check for LLVM

    @alexcrichton
    alexcrichton committed Mar 1, 2019
    Configuration menu
    Copy the full SHA
    6da206b View commit details
    Browse the repository at this point in the history

  2. appveyor: Use VS2017 for all our images 

    Originally added in rust-lang#55935 to test build times, this was reverted
in rust-lang#56201 due to a belief that it caused the exit code 259 spurious
errors. We've since learned, however, that the 259 exit code is likely
not related to this image update as we're getting it in a number of
locations now.

VS2017 looks like it may be required to compile LLVm in the near future,
notably discovered by rust-lang#58408 where we attempted to update LLVM.
    @alexcrichton
    alexcrichton committed Mar 1, 2019
    Configuration menu
    Copy the full SHA
    02b0085 View commit details
    Browse the repository at this point in the history