Closed Bug 995186 Opened 10 years ago Closed 7 years ago

Lower the mochitest-browser-chrome-1 max runtime once devtools is split out

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: emorley, Unassigned)

References

Details

Bug 995060 raised the max runtime for mochitest-browser-chrome-1 to 12000 seconds (up from 4200s). Once the dev tools are split out (bug 984930), we should be able to lower it again significantly (if not to lower than 4200 perhaps?), which will avoid us regressing suite runtimes without realising it, plus save infra wastage when if a harness jams up mid-run and then takes the rest of the 12000 seconds to be killed.
chunk-by-dir is a global change that affects all branches that run mochitest-bc in chunks. Which as of a few days ago is all of them :)

So what we'll need to do is press on with getting the devtools splitting done on Aurora as well (which is also badly affected). Once that's done, we can look at the runtimes on the other release branches and come up with a new timeout that makes sense.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.