Open
Bug 1060189
Opened 11 years ago
Updated 3 years ago
Mochitests should only use the tbplformatter for automation
Categories
(Testing :: Mochitest, defect, P4)
Tracking
(Not tracked)
NEW
People
(Reporter: chmanchester, Unassigned)
Details
Attachments
(1 file)
From bug 1045525 - the mochitest's formatter is really only needed for automation code paths. The mach formatter is probably an appropriate default for running locally.
Comment 1•11 years ago
|
||
I'm all for this. The mach formatter supports output coloring and has a great failure summary. (we should remove that from mochitest/mach_commands.py:384 by the way, to avoid duplicated reporting)
I think that with bug 1045525, the tbpl formatter is dynamically "replaced" by the custom mochitest tbpl formatter? When that lands we'll just have to add --log-tbpl=- in the command line arguments, and use {'mach': sys.stdout} when setting up the logger.
| Reporter | ||
Comment 2•11 years ago
|
||
Here's the patch that does this. I'm a bit concerned this will be perceived as a regression by those running tests locally because the mach formatter doesn't print passing subtests.
Maybe it's time to add a verbosity option to our formatters?
| Reporter | ||
Updated•11 years ago
|
Assignee: nobody → cmanchester
Status: NEW → ASSIGNED
| Reporter | ||
Comment 3•5 years ago
|
||
I'm not planning to pursue this.
Assignee: cmanchester → nobody
Status: ASSIGNED → NEW
Updated•5 years ago
|
Priority: -- → P4
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•