Open Bug 1669931 Opened 5 years ago Updated 4 years ago

Treeherder should show name of failing test case

Categories

(Tree Management :: Treeherder, task)

Tracking

(Not tracked)

People

(Reporter: sg, Unassigned)

Details

I recently got a backout (https://bugzilla.mozilla.org/show_bug.cgi?id=1653276#c28) which mentioned this failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=317944072&repo=autoland&lineNumber=15534

The "summary" (not sure if there is a better name for that) shows:

15534	20:01:57 INFO - GECKO(4664) | Assertion failure: !mOpenRequestActor, at /builds/worker/checkouts/gecko/dom/indexedDB/ActorsChild.cpp:1589
54344	20:36:02 INFO - PROCESS-CRASH | Main app process exited normally | application crashed [@ mozilla::dom::indexedDB::BackgroundDatabaseChild::SendDeleteMeInternal()]
56840	20:36:02 INFO - TEST-UNEXPECTED-FAIL | leakcheck | tab missing output line for total leaks!
60836	20:38:23 ERROR - Return code: 1
60837	20:38:23 ERROR - Got 1 unexpected crashes
60876	[taskcluster:error] exit status 1

What it doesn't show is the name of the test case that was running when the assertion was triggered.

I found that information only by scrolling up ca. 2000 lines in the log to https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=317944072&repo=autoland&lineNumber=13485 where it says:

[task 2020-10-07T19:59:57.968Z] 19:59:57     INFO - TEST-START | toolkit/components/antitracking/test/browser/browser_blockingIndexedDb.js

It would save a lot of time (and avoid mistakes) if this information were already shown in the "summary".

I guess there are cases where this might be ambiguous or a crash is happening outside a test case. Ideally, this piece of information would also be included in the "summary".

Component: Treeherder: Log Parsing & Classification → TreeHerder
You need to log in before you can comment on or make changes to this bug.