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)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: catlee)
Details
(Keywords: sheriffing-P1, Whiteboard: [capacity][simple])
Attachments
(1 file)
1.19 KB,
patch
|
emorley
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
(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 | ||
Updated•11 years ago
|
Assignee: nobody → catlee
Whiteboard: [capacity] → [capacity][simple]
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #739863 -
Flags: review?(emorley)
Reporter | ||
Updated•11 years ago
|
Attachment #739863 -
Flags: review?(emorley) → review+
Assignee | ||
Updated•11 years ago
|
Attachment #739863 -
Flags: checked-in+
Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 2•11 years ago
|
||
This is in production.
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•