Raptor log entries with critical/error end up as INFO in Taskcluster logs
Categories
(Testing :: Raptor, defect)
Tracking
(Not tracked)
People
(Reporter: whimboo, Unassigned)
Details
Here an example:
13:53:45 INFO - raptor-manifest abort: specified test name doesn't exist
13:53:45 INFO - raptor-main abort: no tests found
Whereby the source has:
LOG.critical("abort: specified test name doesn't exist")
We should get this fixed as soon as possible for proper error reporting.
| Reporter | ||
Comment 1•6 years ago
|
||
James, do you have an idea why this is happening? Not sure if it is a mozlog or mozharness issue.
| Reporter | ||
Comment 2•6 years ago
|
||
I think the problem is in the RaptorErrorList in mozharness:
The above case is not covered. Also some entries like raptorError seem to be outdated, given that I cannot find anything like that under testing/raptor. Maybe it was just copy and pasted? Rob, can you remember given that you worked on bug 1455107?
| Reporter | ||
Comment 3•6 years ago
|
||
Here another case:
10:55:43 INFO - raptor-main TEST-UNEXPECTED-FAIL: test 'raptor-tp6m-ebay-kleinanzeigen-search-geckoview-cold' timed out loading test page: https://m.ebay-kleinanzeigen.de/s-anzeigen/auf-zeit-wg-berlin/zimmer/c199-l3331 pending metrics: fcp, fnb paint, dcf, load time
10:55:43 ERROR - Return code: 1
Comment 4•6 years ago
|
||
Yes, I think you're correct; this is mozharness parsing the logs and re-emitting them at the wrong level.
Comment 5•6 years ago
|
||
Yes definitely needs to be addressed. I believe this is the same issue as Bug 1522604 - Add proper support for LOG.error (which marauder is currently working on)? If you agree please close this as a duplicate, thanks!
| Reporter | ||
Comment 6•6 years ago
|
||
It would have been good if that other bug was mentioned in our last Raptor meeting. So I wouldn't have filed a dupe in the first place. But yes, lets continue on that.
Verified duplicate
Description
•