Closed Bug 822821 Opened 11 years ago Closed 11 years ago

Lower build step timeout & maxTime to avoid runaway builds

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: catlee)

Details

(Keywords: sheriffing-P1, Whiteboard: [capacity][simple])

Attachments

(1 file)

(In reply to Chris AtLee [:catlee] from bug 820769 comment #16)
> (In reply to Ed Morley [UTC+0; email:edmorley@moco] from comment #12)
> > (In reply to Chris AtLee [:catlee] from comment #11)
> > > (In reply to Ed Morley [UTC+0; email:edmorley@moco] from comment #2)
> > > > catlee, should we be aborting the build sooner than 7+ hrs in? (comment 1)
> > > 
> > > what's a reasonable upper limit for builds these days? 7 hours probably
> > > comes from the era of PGO-builds-on-slow-VMs.
> > 
> > Win PGO is the long pole - looking at the last half dozen jobs on m-c (mins):
> > 224, 231, 217, 225, 222, 217
> > 
> > Happy for me to file a bug to lower max runtime to say 270 mins/4.5 hrs?
> 
> Sounds good, thanks!
> 
> This was set to 3 hours in
> http://hg.mozilla.org/build/buildbotcustom/rev/65e500d98367.
> 
> Can we set a maxTime of 4.5 hours, and lower the timeout back down to 2
> hours?
Assignee: nobody → catlee
Whiteboard: [capacity] → [capacity][simple]
Attachment #739863 - Flags: review?(emorley)
Attachment #739863 - Flags: review?(emorley) → review+
Attachment #739863 - Flags: checked-in+
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
This is in production.
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: