Closed
Bug 979512
Opened 11 years ago
Closed 11 years ago
Add a command line option to split the tests and run a specified chunk
Categories
(Remote Protocol :: Marionette, defect)
Remote Protocol
Marionette
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla31
People
(Reporter: davehunt, Assigned: davehunt)
References
Details
Attachments
(1 file, 3 obsolete files)
5.63 KB,
patch
|
davehunt
:
review+
|
Details | Diff | Splinter Review |
It looks like we're going to need to split the manifest when running Gaia UI tests against emulators on TBPL due to us hitting the 2 hour build limit. Rather than split up the manifest files manually and have to maintain these separate files, it would be good to control this via a command line option.
I'm thinking something like --chunk=1:4 where the tests selected to run would be split into four groups, as equal in number as possible, and the first group would be run. Subsequent (or parallel) jobs using --chunk=2:4 etc would run the remaining groups.
So long as all jobs are running on the same revision then the groups can be trusted not to overlap or omit tests.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → dave.hunt
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #8388459 -
Flags: review?(jgriffin)
Comment 2•11 years ago
|
||
Comment on attachment 8388459 [details] [diff] [review]
Add a command line option to split the tests and run a specified chunk. v1.0
Review of attachment 8388459 [details] [diff] [review]:
-----------------------------------------------------------------
::: testing/marionette/client/marionette/runner/base.py
@@ +975,5 @@
> if self.marionette.check_for_crash():
> break
>
> def run_test_sets(self):
> + run_chunk, total_chunks = [int(s) for s in self.chunk.split(':')]
Can we use this_chunk instead of run_chunk to be consistent with mochitest and other harnesses?
Attachment #8388459 -
Flags: review?(jgriffin) → review+
Assignee | ||
Comment 3•11 years ago
|
||
Carried r+
Attachment #8388459 -
Attachment is obsolete: true
Attachment #8389137 -
Flags: review+
Assignee | ||
Comment 4•11 years ago
|
||
Before landing this, I notice that mochitest uses --this-chunk and --total-chunks command line options. Do we want to simply use that rather than introduce a strictly formatted string? My initial thinking was that it would be better to keep the number of command line options to a minimum, but the two arguments would be less error prone and would be consistent with mochitests.
Flags: needinfo?(jgriffin)
Comment 5•11 years ago
|
||
dave and I discussed and agreed it made sense to use the same argument names as mochitest, for consistency's sake.
Flags: needinfo?(jgriffin)
Assignee | ||
Comment 6•11 years ago
|
||
Attachment #8389137 -
Attachment is obsolete: true
Attachment #8392208 -
Flags: review?(jgriffin)
Updated•11 years ago
|
Attachment #8392208 -
Flags: review?(jgriffin) → review+
Assignee | ||
Updated•11 years ago
|
Keywords: checkin-needed
Comment 7•11 years ago
|
||
Keywords: checkin-needed
Whiteboard: [fixed-in-fx-team]
Comment 8•11 years ago
|
||
Comment 9•11 years ago
|
||
And other bustage:
https://tbpl.mozilla.org/php/getParsedLog.php?id=36389402&tree=Fx-Team
Please make sure this passes on Try before re-requesting checkin.
Whiteboard: [fixed-in-fx-team]
Assignee | ||
Comment 10•11 years ago
|
||
Carrying r+ running on try: https://tbpl.mozilla.org/?tree=Try&rev=7fb1e0c74d74
Attachment #8392208 -
Attachment is obsolete: true
Attachment #8393668 -
Flags: review+
Assignee | ||
Comment 11•11 years ago
|
||
Sorry for that silly mistake Ryan, try looks good now.
Keywords: checkin-needed
Comment 12•11 years ago
|
||
Keywords: checkin-needed
Comment 13•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla31
Updated•2 years ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•