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

Failure to upload to S3 from AppVeyor #39074

Closed
alexcrichton opened this issue Jan 15, 2017 · 3 comments
Closed

Failure to upload to S3 from AppVeyor #39074

alexcrichton opened this issue Jan 15, 2017 · 3 comments
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason)

Comments

@alexcrichton
Copy link
Member

alexcrichton commented Jan 15, 2017

Seen twice now with the failure message:

A WebException with status ReceiveFailure was thrown.

Logs:

I'll probably email them about retries and such come next week, wanted to start collecting logs in the meantime.

@alexcrichton alexcrichton added the A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) label Jan 15, 2017
@brson
Copy link
Contributor

brson commented Jan 18, 2017

sigh

@alexcrichton
Copy link
Member Author

We've got enough examples now I've opened a thread with AppVeyor about this.

@alexcrichton
Copy link
Member Author

An upstream issue has been created for this.

alexcrichton added a commit to alexcrichton/rust that referenced this issue Mar 23, 2017
This was recently implemented (appveyor/ci#1387) in response to one of our
feature requests, so let's take advantage of it! I'm going to optimistically
say...

Closes rust-lang#39074
bors added a commit that referenced this issue Mar 23, 2017
appveyor: Leverage auto-retry to upload to S3

This was recently implemented (appveyor/ci#1387) in response to one of our
feature requests, so let's take advantage of it! I'm going to optimistically
say...

Closes #39074
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)
Projects
None yet
Development

No branches or pull requests

2 participants