Hi, > The download failure rate gets skewed when the MD5's become out of date > because folks try again right away, maybe even more than once and get the > same failure. About 1/3rd of people try again, 2/3rd give up I would assume (pageview vs unique pageview).
> The MD5Checker seems to work, but the CI server keeps hanging saving the > artifacts of the flex-sdk-release build and then MD5Checker doesn't get to > run. Can we make this more reliable by have it use a pre built SDK? > But really, the theme remains that download reliability is poor. Downloading from multiple locations probably makes the issue worse, having multiple points of failure, but it seems odd the majority of MD5 failures are for our SDK - except when the player changes. > I'm starting to wonder if there is a bug in URLLoader that makes it less > forgiving in large downloads. That also seems likely to me. > Maybe we need to implement some other, more reliable download mechanism. Chunking and check sums for each chunk and re-sended any that fail? Although seems like a lot of effort to go to. Thanks, Justin
