Closed
Bug 1458105
Opened 6 years ago
Closed 6 years ago
Gecko Decision task bustage on Autoland
Categories
(Firefox Build System :: Task Configuration, task)
Tracking
(firefox61 fixed)
RESOLVED
FIXED
mozilla61
Tracking | Status | |
---|---|---|
firefox61 | --- | fixed |
People
(Reporter: dluca, Assigned: dustin)
References
Details
Attachments
(1 file)
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → dustin
Comment hidden (mozreview-request) |
Comment 2•6 years ago
|
||
mozreview-review |
Comment on attachment 8972208 [details] Bug 1458105 - try more to fetch automationrelevance; https://reviewboard.mozilla.org/r/240872/#review246650
Attachment #8972208 -
Flags: review?(gps) → review+
Comment 3•6 years ago
|
||
hg error in cmd: hg pull upstream: pulling from https://hg.mozilla.org/integration/autoland searching for changes abort: HTTP Error 500: Internal Server Error
Assignee | ||
Comment 4•6 years ago
|
||
Well, isn't that a coincidence? I'll happily review a patch to make autoland retry more!
Comment 5•6 years ago
|
||
I suspect the elevated error rates are due to us replacing 2 beefy hgweb servers with 2 not-as-beefy servers. I'll VPN in and put the beefy servers back in service. We can look at the logs tomorrow to see what capacity issues were in play.
Pushed by gszorc@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6f975a367b79 try more to fetch automationrelevance; r=gps
Comment 7•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/6f975a367b79
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox61:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
Comment 8•6 years ago
|
||
From IRC logs yesterday I gather that this was the issue that cause: ReadTimeout: HTTPSConnectionPool(host='hg.mozilla.org', port=443): Read timed out on try. And the fix is: A) gps rolling back to using beefy machines, B) ensure requests are retried more than twice.
Comment 10•6 years ago
|
||
We had some capacity problems on hg.mo. We mitigated those last week. We also landed a commit to retry harder. So double mitigation. We may still see sporadic failures on Try and older release repos due to old code only retrying twice.
Updated•5 years ago
|
Version: Version 3 → 3 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•