-
Notifications
You must be signed in to change notification settings - Fork 69
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
Network errors impacting mason downloads #516
Comments
|
@springmeyer I was on OSX and saw hangs with clang++ when using the following curl command:
The connection to the file is made relatively quick, but the 30MB download takes much longer than other 30MB files. |
@mapsam, okay thanks for the details. After 1727795 mason will now output the exact returncode on error. This is what is producing the:
Above in the error I saw in @artemp's commit where the android SDK failed to download. Let's keep an eye on whether we always see |
Not an s3 issue, but noting nonetheless that I also just hit this on an OS X travis job:
Which looks like a git clone failing in curl, also with |
Now seeing:
|
ugh, also just hit:
|
hrm:
https://travis-ci.org/mapbox/node-cpp-skel/jobs/305550318#L552 |
Do you have any way to observe the S3 connections or S3 errors more directly? All the error codes you've got here appear to be from downstream applications that are perhaps reacting to S3 networking failures. But even the 429 isn't an S3 response code -- they give you a 503 if they want you to |
We are using curl on the command line to download the binary Lines 533 to 544 in 2602c30
In 1727795 I modified things to actually try to print the http error code.
That one ( |
I think I'd have to take it to AWS support. You might try to check for |
Thanks @rclark - signing off for the holiday now. I will add |
another one, which looks only related to travis network since the upstream is not coming from AWS. I probably won't post more of this kind to avoid being too noisy on this ticket, but will post this one since I've not seen it before:
|
|
Error message in Travis when trying to download recently published LLVM 6.0.0 binaries:
Note: (returncode: 141) |
I feel like I've been seen an increased amount of network failures when fetching binaries from s3 in the last month +. This ticket stands to track these to start assembling a fuller picture of the failures and see if there is a pattern.
The text was updated successfully, but these errors were encountered: