Increase vcssync gexport timeout

RESOLVED FIXED

Status

Release Engineering
Mozharness
RESOLVED FIXED
a year ago
11 months ago

People

(Reporter: dhouse, Assigned: dhouse)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

a year ago
Created attachment 8867290 [details] [diff] [review]
bugX_2hr-gexport-timeout-mozharness.patch

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 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+
(Assignee)

Comment 2

11 months ago
Comment on attachment 8867290 [details] [diff] [review]
bugX_2hr-gexport-timeout-mozharness.patch

Thanks Hal!
Attachment #8867290 - Flags: checked-in+
(Assignee)

Updated

11 months ago
Status: NEW → RESOLVED
Last Resolved: 11 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.