Closed
Bug 1364514
Opened 7 years ago
Closed 7 years ago
Increase vcssync gexport timeout
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Release Engineering
Applications: MozharnessCore
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dhouse, Assigned: dhouse)
References
Details
Attachments
(1 file)
1021 bytes,
patch
|
hwine
:
review+
dhouse
:
checked-in+
|
Details | Diff | Splinter Review |
vcs-sync gexport has timed out on both gecko-dev and gecko-projects conversions multiple times in the past few months. The spin-up for the gexports (40 minutes in one case) can approach and exceed the timeout, and that causes the sync to stall or lag behind. For gecko-dev and gecko-projects, I manually increased the global gexport timeout (not a config setting) to 120 minutes to allow the gexports to complete. Now the conversions will complete a larger batch at once and not incrementally chip at it, after each long spin-up. I'm expecting that 2 hours is long enough for current large updates and short enough to expose an actual failure. This change is to make the 2 hour timeout on gexport permanent(not a local change on vcssync1/2) and global. I also increased the default git push timeout to 90 minutes to avoid a timeout on push.
Attachment #8867290 -
Flags: review?(hwine)
Comment 1•7 years ago
|
||
Comment on attachment 8867290 [details] [diff] [review] bugX_2hr-gexport-timeout-mozharness.patch Review of attachment 8867290 [details] [diff] [review]: ----------------------------------------------------------------- lgtm - sorry I forgot to mark bugzilla that I was on PTO
Attachment #8867290 -
Flags: review?(hwine) → review+
Comment on attachment 8867290 [details] [diff] [review] bugX_2hr-gexport-timeout-mozharness.patch Thanks Hal!
Attachment #8867290 -
Flags: checked-in+
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•