Closed Bug 810760 Opened 12 years ago Closed 12 years ago

Don't <br /> jetpack results

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Assigned: philor)

Details

Attachments

(2 files)

This is, of course, madness, but it's the multidirectional reverse-engineered madness we live in. Tinderbox was a giant table that nobody would touch, so to avoid widening the table cells, buildbot summarized results with "TinderboxPrint: %s<br/>%s\n" (or %s:%s, because a foolish constancy etc.). tbpl learned that it could dig out results by looking for /(.*)(\:|<br\/>)(.*)/. Jetpack's results, rather than having the invalid <br/>, have the invalid but typically, at least at the time, ignored by validators <br />. As a result, given the right screen width and tbpl's use of columns for the scrape, they display as * s: talos-r3-fed-071 5712/0 * jetpack because tbpl doesn't recognize them as results, and doesn't strip them down into "jetpack: 5712/0" like it would for <br/>.
Attached patch buildbotcustomSplinter Review
Attachment #680533 - Flags: review?(catlee)
Attached patch toolsSplinter Review
Attachment #680534 - Flags: review?(catlee)
Attachment #680534 - Flags: review?(catlee) → review+
Attachment #680533 - Flags: review?(catlee) → review+
This is in production now.
Okay, thanks!
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: