Closed
Bug 953254
Opened 11 years ago
Closed 11 years ago
split mochitest-browser-chrome test job into 2 or more pieces
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 819963
People
(Reporter: jfkthame, Unassigned)
Details
It's noticeable that of the various unit tests on TBPL, the "M(bc)" run is consistently the long pole, typically taking around 35-50 minutes on desktop Opt jobs, and 100-140 minutes on Debug. I propose that we should split this into bc1 and bc2 (or even 3-4) jobs that can be run in parallel on different slaves, in order to improve end-to-end time. The current Debug mochitest-bc time is especially painful when an orange appears and retriggers are needed to determine whether it's consistent.
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•6 years ago
|
Component: Mochitest Chrome → Mochitest
You need to log in
before you can comment on or make changes to this bug.
Description
•