Closed Bug 803466 Opened 12 years ago Closed 9 years ago

TBPL logs don't show pymake failures

Categories

(Tree Management Graveyard :: TBPL, defect)

All
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: glandium, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: sheriffing-P1)

See https://tbpl.mozilla.org/php/getParsedLog.php?id=16257848&tree=Try&full=1 for example. There are many pymake failure messages in there, in the form "path:line: command 'command' failed, return code n" , and none are highlighted, which makes it very hard to find errors in pymake builds.

Relatedly, when failures don't happen in the build part, usually, errors are not highlighted either, and the best bet is to look for the "Finished xxxxxx failed" to know what part of the tinderbox script failed. It might be helpful to highlight those as well, or at the very least, do so in the absence of any other error highlight.
Summary: Tinderbox logs don't show pymake failures → TBPL logs don't show pymake failures
Component: Release Engineering → Tinderboxpushlog
Product: mozilla.org → Webtools
What should we be parsing on here?

Current regex is:
https://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/file/43b5054776ba/php/inc/GeneralErrorFilter.php#l25
Blocks: 778688
Whiteboard: [sheriff-want]
I guess, something like:
/command '.*' failed, return code \d+$/

And
/========= Finished .* failed/
Keywords: sheriffing-P1
Whiteboard: [sheriff-want]
Product: Webtools → Tree Management
Version: other → unspecified
TBPL has been EOLed (bug 1054977).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
More importantly, pymake has been EOLed. Because if it hadn't been, that'd likely still be a relevant bug against treeherder's log viewer.
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.