Closed
Bug 1091627
Opened 11 years ago
Closed 11 years ago
Understanding ./mach xpcshell-test output is near impossible due to amount of console spam
Categories
(Testing :: XPCShell Harness, defect)
Testing
XPCShell Harness
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1091413
People
(Reporter: standard8, Unassigned)
Details
(Keywords: dogfood)
Attachments
(1 file)
|
307.87 KB,
image/png
|
Details |
On a reasonable sized console, trying to read and understand the output of single
test run is so bad its near impossible.
See the attached log for an example running:
./mach xpcshell-test browser/components/loop/test/xpcshell/test_loopservice_busy.js
Whilst there may be things like unexpected javascript warnings, repeating the same command information over and over again isn't right nor helpful.
Marking as blocker, as this is just wasting developer time - I can just about find *my* errors in the test, but finding real output is really difficult.
Comment 1•11 years ago
|
||
I think this is a dupe up bug 1091413, but the severity is well taken. I will post a patch to fix this today, but as an immediate workaround passing '--log-tbpl -' to mach will result in a less noisy output format for the single test case.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•