Closed Bug 1048985 Opened 10 years ago Closed 6 years ago

Mozharness/buildbotcustom should match against TEST-UNEXPECTED-FAIL even if not at start of the line

Categories

(Release Engineering :: Applications: MozharnessCore, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: emorley, Unassigned)

References

(Blocks 1 open bug)

Details

Broken out from bug 1048423 comment 2 & also bug 1028119 comment 8.

tl;dr if the harness missed a TEST-UNEXPECTED-FAIL, the job will still turn orange iff the TEST-UNEXPECTED-FAIL is at the start of the line.

In an ideal world the harness would be perfect, and we'd rely solely on it's summary and the return code, however whilst we still check for TEST-UNEXPECTED-FAIL within mozharness/buildbotcustom, we should just remove the start of line anchor.

mozharness:
http://mxr.mozilla.org/build-central/search?string=TEST-UNEXPECTED&case=1&find=%2Fmozharness%2F&findi=&filter=^[^\0]*%24&hitlimit=&tree=build-central

buildbotcustom:
http://mxr.mozilla.org/build-central/search?string=TEST-UNEXPECTED&case=1&find=%2Fbuildbotcustom%2F&findi=&filter=^[^\0]*%24&hitlimit=&tree=build-central
Summary: Mozharness/buildbotcustom should match against TEST-UNEXPECTED-FAIL even if it at start of the line → Mozharness/buildbotcustom should match against TEST-UNEXPECTED-FAIL even if not at start of the line
Fixing this would allow us to switch structured logging back for the harness-generated logs (where we switched to unstructured logs because of the formatting difference).
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.