|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I did three experiments by using ab (http://httpd.apache.org/docs/2.2/programs/ab.html) and do stress tests of download the artifacts 300 times:
1. Download artifacts from jenkins (18 failures out of 300 requests)
2. Download artifacts from jenkins proxy by apache (9 failures out of 300 requests)
3. Download the same files from IIS server, without going though jenkins. (0 failures out of 300 requests)
ab -n300 -c2 http://xxxx.EXE
So based on the above result, we can say that there is issue with jenkins download. The artifacts are 150-300MB. We are downloading it by putting server in US and download from China. I don't believe this is caused by network issue. Because if it is network issue, we will get corrupted download other than a a complete download but file size if wrong. Or we can say that poor network could trigger jenkins bug.