822821 - Lower build step timeout & maxTime to avoid runaway builds

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Ed Morley [:emorley]]

(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?

Comment 1

[Chris AtLee [:catlee]]

Attachment: decrease timeouts for builds

Comment 2

[Aki Sasaki (not active)]

This is in production.