Module: testDirectUpdate_Download Test: /testDirectUpdate/test2.js Failure: Update has been finished downloading. Branches: mozilla-beta Platforms: Windows Vista Report: http://mozmill-release.blargon7.com/#/update/report/837c1e0f361ac93453ee6972197ff646
Created attachment 810429 [details] log.txt From this log I'd say the download itself went *very* slow.
Sadly I had to remove all the old build directories due to disk space issues on master. So we don't have the http log available anymore. :/ No way to figure out which server caused this problem. This is indeed not a failure on our side and I don't think we should increase the timeout. Those servers have to be checked instead. Lets keep an eye on it.
This actually failed several times: http://mozmill-release.blargon7.com/#/update/report/837c1e0f361ac93453ee697219813da9 http://mozmill-release.blargon7.com/#/update/report/837c1e0f361ac93453ee697219810dbd And once with a disconnect error: http://mozmill-release.blargon7.com/#/update/report/837c1e0f361ac93453ee69721984de6b I can't gather more console logs from Jenkins: > No such file: /home/mozauto/mozmill-ci/./jenkins-master/jobs/ondemand_update/builds/2013-09-25_11-05-48/log I get this even for the log I uploaded a few minutes ago :|
Oh, thanks Henrik for the update. I manually downloaded the update, and it came slower then I would have expected, but not enough to make our tests crash. We should keep an eye out if this fails again, might be problems with the CDN? (Well if they are I expect they would be noticed elsewhere as well)
Downloaded from where? In such a case please enable http logs please so we get more information from which server the data is downloaded from.
The .mar file from the AUS update.xml file. I only tried downloading to see if it is (or not) available, by "slower than I would have expected" I mean about 0.6-0.8 MBPS. Nothing conclusive here.
Mozmill tests have been superseded by Marionette tests.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.