Closed
Bug 523394
Opened 16 years ago
Closed 16 years ago
debug builds spit out lots of output, confuse tinderbox error parser
Categories
(Webtools Graveyard :: Tinderbox, defect)
Webtools Graveyard
Tinderbox
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ted, Assigned: ted)
References
()
Details
Attachments
(1 file)
|
1.41 KB,
patch
|
cls
:
review+
|
Details | Diff | Splinter Review |
You can look at any Tinderbox log of a debug unittest run to see this, but the "error summary" section is just absolutely full of junk. There are probably a few root causes here:
1) Error console output goes to stdout
2) strict JavaScript mode is on
3) Random debug printfs that have "Error: " in them somewhere
We need to fix this in some way, or nobody will ever be able to look at a Tinderbox log usefully.
I'd say the tinderbox error parser should probably be a little stricter.
| Assignee | ||
Updated•16 years ago
|
Assignee: nobody → ted.mielczarek
Component: General → Tinderbox
Product: Core → Webtools
QA Contact: general → tinderbox
| Assignee | ||
Comment 2•16 years ago
|
||
Indeed, this simple patch takes this log:
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox-Unittest/1256182254.1256186574.13089.gz#err48
down to just 4 lines of detected errors, the TEST-UNEXPECTED-FAIL lines.
Only the one removal is strictly necessary, but we're not actually using those old mochitest/reftest/xpcshell test failure lines anymore anyway.
Attachment #407758 -
Flags: review?(cls)
| Assignee | ||
Updated•16 years ago
|
Status: NEW → ASSIGNED
Attachment #407758 -
Flags: review?(cls) → review+
| Assignee | ||
Comment 3•16 years ago
|
||
Checking in ep_unittest.pl;
/cvsroot/mozilla/webtools/tinderbox/ep_unittest.pl,v <-- ep_unittest.pl
new revision: 1.5; previous revision: 1.4
done
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 4•16 years ago
|
||
Filed bug 523974 on getting tinderbox.mozilla.org updated.
Updated•11 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•