-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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.
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
Switch AppVeyor to the standard Visual Studio 2017 image #61972
Conversation
We were previously using the preview image but there doesn't seem to be a reason why, as the commit that originally added it didn't replace the standard image, but just used the preview from the start. AppVeyor Support recommended switching to the standard image in this support thread: https://help.appveyor.com/discussions/problems/24057-build-job-has-failed-to-start-but-backup-cloud-is-not-configured#comment_47365011
@bors p=1 |
@bors: r+ |
📌 Commit 13dc0ba has been approved by |
⌛ Testing commit 13dc0ba with merge fda46cd67a51d55db8fa95a839e72d3aa26e2597... |
💔 Test failed - status-appveyor |
Failure log: failures:
---- [debuginfo-gdb+lldb] debuginfo\basic-types-globals-metadata.rs stdout ----
NOTE: compiletest thinks it is using LLDB version 800
NOTE: compiletest thinks it is using LLDB without native rust support
error: Error while running LLDB
status: exit code: 1
command: "C:\\Python27\\python2.7" "C:\\projects\\rust\\src/etc/lldb_batchmode.py" "C:\\projects\\rust\\build\\i686-pc-windows-gnu\\test\\debuginfo\\basic-types-globals-metadata\\a.exe" "C:\\projects\\rust\\build\\i686-pc-windows-gnu\\test\\debuginfo\\basic-types-globals-metadata\\basic-types-globals-metadata.debugger.script"
stdout:
------------------------------------------
------------------------------------------
stderr:
------------------------------------------
Traceback (most recent call last):
File "C:\projects\rust\src/etc/lldb_batchmode.py", line 17, in <module>
import lldb
ImportError: No module named lldb
------------------------------------------ |
Hm I don't believe we should be running LLDB tests on Windows, so some auto-detection may be automatically enabling them and we'll need to disable that on the CI builders. |
Switch AppVeyor to the standard Visual Studio 2017 image We were previously using the preview image but there doesn't seem to be a reason why, as the commit that originally added it didn't replace the standard image, but just used the preview from the start. AppVeyor Support recommended switching to the standard image [in this support thread](https://help.appveyor.com/discussions/problems/24057-build-job-has-failed-to-start-but-backup-cloud-is-not-configured#comment_47365011). r? @alexcrichton fixes #61931
💔 Test failed - status-appveyor |
Same failure as last time. Would need to r- ? |
@bors r- Why was this even tested a second time. |
Not relevant anymore. |
We were previously using the preview image but there doesn't seem to be a reason why, as the commit that originally added it didn't replace the standard image, but just used the preview from the start.
AppVeyor Support recommended switching to the standard image in this support thread.
r? @alexcrichton
fixes #61931