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

Build job has failed to start on AppVeyor #61931

Closed
pietroalbini opened this issue Jun 18, 2019 · 4 comments
Closed

Build job has failed to start on AppVeyor #61931

pietroalbini opened this issue Jun 18, 2019 · 4 comments
Assignees
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@pietroalbini
Copy link
Member

We had a couple builds in the past few days where AppVeyor failed to start a build, giving us an empty log and a "Build job has failed to start, but backup cloud is not configured." message.

@pietroalbini pietroalbini added A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. C-bug Category: This is a bug. labels Jun 18, 2019
@pietroalbini
Copy link
Member Author

@pietroalbini
Copy link
Member Author

Seems like the issue only appeared on their GCP builders, so I opened a PR (#61972) to switch to their Hyper-V ones, as they recommended.

bors added a commit that referenced this issue 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
@pietroalbini
Copy link
Member Author

AppVeyor said the issue might start to happen again.

@pietroalbini
Copy link
Member Author

Well, this is not a problem anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant