Closed
Bug 445610
Opened 16 years ago
Closed 16 years ago
TinderboxPrint:s should highlight failures so multiple failures caught faster
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dbaron, Assigned: ted)
Details
Attachments
(1 file)
4.35 KB,
patch
|
rcampbell
:
review+
|
Details | Diff | Splinter Review |
When we print a failed test result using "TinderboxPrint" in the various tests we do on tinderbox, we should put in inside a span that is styled so that it shows up more clearly. I want this because it helps diagnosing multiple failures. A cell in the tinderbox waterfall turns orange when it has one or more failures. When there is more than one failure at the same time, we often fail to notice until after the first failure is fixed ("oh, that didn't make it go green, whoops, there was a second failure the whole time"). We could fix these more quickly if the tinderbox UI made us more likely to notice them. For example, if the reftests fail on a build, instead of printing just: reftest: 1971/3/71 we could print: <em style="testfail">reftest: 1971/3/71</em> where we had style like: em.testfail { background: black; color: red; } then if both reftests and chrome tests failed in the same build, we'd be more likely to notice that there were two separate things failing.
Assignee | ||
Comment 1•16 years ago
|
||
someone suggested at some point that we highlight the failed number in red.
Assignee | ||
Comment 2•16 years ago
|
||
This should provide the necessary style hook. We'll need to stick the actual style somewhere on tinderbox.
Assignee: nobody → ted.mielczarek
Status: NEW → ASSIGNED
Attachment #330025 -
Flags: review?(rcampbell)
Comment 3•16 years ago
|
||
Comment on attachment 330025 [details] [diff] [review] surround testfail results with em class="testfail" OK
Attachment #330025 -
Flags: review?(rcampbell) → review+
Assignee | ||
Comment 4•16 years ago
|
||
Checked in, going to require another unittest master restart to pick this up, though.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•16 years ago
|
Component: Testing → Release Engineering
Product: Core → mozilla.org
QA Contact: testing → release
Version: Trunk → other
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•