Closed Bug 1265921 Opened 9 years ago Closed 8 years ago

Selecting a failed job with the new "unsuccessful execution steps" thing, then selecting a still-running job does weird things.

Categories

(Tree Management :: Treeherder, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: KWierso, Assigned: camd)

Details

If you load https://treeherder.mozilla.org/#/jobs?repo=mozilla-aurora&fromchange=133c7279577b12d9814cbebdd09d529f7c75a0f6&group_state=expanded&filter-searchStr=r24&selectedJob=2408493 and let it load, then select one of the still-running jobs, the failure summary pane still shows the "Unsuccessful execution steps" thing from the previous job, in addition to the running job's "no logs available for this job".
Component: Treeherder → Treeherder: Log Parsing & Classification
Hi Christian, I see the failures linked in comment 1 were classified against this bug. This bug is unrelated. In this case Taskcluster in this case didn't produce log output that matched the known parser format, so the way to handle this is to open the log viewer and scroll to the end to see what error occurred. At that point there will normally be two bugs to file: (1) for the possibly intermittent taskcluster/... failure, (2) for making taskcluster/... output more useful logs in this case. Also when manually classifying, I'd look at the age of the bug - which in this case was so long ago (and with no log output that looked the same as that log) that it was unlikely to be related. Hope that helps :-) (The unrelated issue in comment 0 must have been fixed a while ago, since I can't repro - marking WFM).
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(cbrindusan)
Resolution: --- → WORKSFORME
It helps a lot, thank you :-)
Flags: needinfo?(cbrindusan)
Component: Treeherder: Log Parsing & Classification → TreeHerder
You need to log in before you can comment on or make changes to this bug.