Closed Bug 669185 Opened 13 years ago Closed 13 years ago

mobile-browser-chrome should include the same em class="testfail" around the failed test count that everything else does

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Platform:
ARM
Android
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Assigned: coop)

Details

(Whiteboard: [unittest])

Attachments

(1 file)

Markup failures in mobile-browser-chrome summary
880 bytes, patch
bear
: review+
coop
: checked-in+
Details | Diff | Splinter Review 
All the other suites output the summary as "20025/<em class="testfail">2</em>/7" which winds up on tbpl as black/red/black. browser-chrome on Android skips the <em class="testfail"></em>, which seems like nothing, but every single time I look at a failed run, I have a moment's hesitation when I glance at the summary to see how many failures I need to find to star.
Assignee: nobody → coop
Priority: -- → P3
Whiteboard: [unittest]
Status: NEW → ASSIGNED
Priority: P3 → P2
Attachment #558643 - Flags: review?(bear) → review+
Comment on attachment 558643 [details] [diff] [review]
Markup failures in mobile-browser-chrome summary

https://hg.mozilla.org/build/buildbotcustom/rev/41fb8c1b1185
Attachment #558643 - Flags: checked-in+
Merged to production and reconfigured.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: