1075641 - Many successful try jobs have logs that have not yet been parsed

Status: RESOLVED DUPLICATE of bug 1074927

(Tree Management :: Treeherder, defect)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

I pushed talos to try:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=70b2b4d44f4f

results came in to tbpl, but here I get "log parsing not complete".  On another try push of unittests:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=228f7e1c31a3

I get logs for failures right away, but not for success jobs.

the use case of running talos on try is that it will be green 99% of the time and we want to click on the job to see the summary of the results printed.  Finding these on a graph is not useful, just seeing the raw results printed in the summary/details pane is needed.

this would be required before we turn off tbpl, but it is not needed right now.

Comment 1

[Ed Morley [:emorley]]

Successful jobs are parsed, but just by a worker with a lower priority (and I believe the lower priority is the right thing to do). The root cause here is just that the parser is getting behind (so we need more workers and/or perf optimisations), and that clicking a job to view it in the job details panel doesn't bump the priority - both of which are covered by bug 1074927. 

Thank you for filing this, it's good to know other use cases it impacts and thus increases the priority of bug 1074927.

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

will we process logs for success jobs on try as well, or just production trees?

Comment 3

[Ed Morley [:emorley]]

We already parse all logs on all trees, whatever their result, and will continue to do so. It's just a case of there being a backlog of queued tasks, since parsing occurs asynchronously.