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.

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

Closed
wants to merge 1 commit into from

Conversation

pietroalbini
Copy link
Member

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

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
@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jun 19, 2019
@pietroalbini
Copy link
Member Author

@bors p=1

@alexcrichton
Copy link
Member

@bors: r+

@bors
Copy link
Contributor

bors commented Jun 20, 2019

📌 Commit 13dc0ba has been approved by alexcrichton

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jun 20, 2019
@bors
Copy link
Contributor

bors commented Jun 20, 2019

⌛ Testing commit 13dc0ba with merge fda46cd67a51d55db8fa95a839e72d3aa26e2597...

@bors
Copy link
Contributor

bors commented Jun 20, 2019

💔 Test failed - status-appveyor

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Jun 20, 2019
@tesuji
Copy link
Contributor

tesuji commented Jun 20, 2019

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
------------------------------------------

@alexcrichton
Copy link
Member

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.

@bors
Copy link
Contributor

bors commented Jun 21, 2019

⌛ Testing commit 13dc0ba with merge 4ceba1d...

bors added a commit that referenced this pull request Jun 21, 2019
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
@bors
Copy link
Contributor

bors commented Jun 21, 2019

💔 Test failed - status-appveyor

@tesuji
Copy link
Contributor

tesuji commented Jun 21, 2019

Same failure as last time. Would need to r- ?

@pietroalbini
Copy link
Member Author

@bors r-

Why was this even tested a second time.

@bors bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jun 21, 2019
@pietroalbini
Copy link
Member Author

Not relevant anymore.

@pietroalbini pietroalbini deleted the appveyor-vs2017 branch July 1, 2019 07:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Build job has failed to start on AppVeyor
5 participants