Closed Bug 422878 Opened 17 years ago Closed 15 years ago

add ep_sisyphus.pl to handle tinderbox error parsing

Categories

(Testing Graveyard :: Sisyphus, defect)

x86
All
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: bc, Assigned: bc)

References

Details

<http://lxr.mozilla.org/mozilla/source/webtools/tinderbox/> contains the error parsers used for scraping errors from the logs submitted to tinderbox. A new error parser is needed to handle the sisyphus style output which contains a cvs update log of sisyphus and the js tests but currently no build log. The operative pattern to flag as an error line is of the form: TinderboxPrint:.*F:([0-9]*) R:([0-9])* where the R (regression count) value is greater than 0. much of <http://lxr.mozilla.org/mozilla/source/webtools/tinderbox/ep_unittest.pl> can be retained as is with the addition of a section to sub has_errorline to find the TinderboxPrint showing non-zero regressions. This needs to be completed before the js tests can be moved from the MozillaTest tinderbox. Rob, how is the tinderbox configured to know which error parser to use for a log ?
Flags: in-testsuite-
Flags: in-litmus-
Note that http://lxr.mozilla.org/mozilla/source/webtools/tinderbox/Makefile will need ep_sisyphus.pl added to the FILES= list.
Mass move of Sisyphus bugs to Testing : Sisyphus. Filter on SisyphusMassMove to ignore.
Component: Testing → Sisyphus
Flags: in-litmus-
Product: Core → Testing
QA Contact: testing → sisyphus
no longer relevant.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.