A "crash" action from mozlog should to be more than enough to fail a job.

(In reply to Chris Manchester [:chmanchester] from comment #1) > Created attachment 8490833 [details] [diff] [review] > Add action counts to mozlog status handler to account for crashes. I think this is what we want here. This will let individual harnesses decide whether to include test_status in final counts and avoids introducing a new set of well known strings that represent statuses. I don't think the mozharness consumer will get significantly more complicated as a result, but let's see.

This gets rid of special strings just for mozlog. I think the failure conditions based on the summary are pretty straightforward. Down the road just a little bit we might want moztest to have an idea of results processing that replaces that in mozharness altogether. Here it is on ash turning marionette desktop orange with the patch from bug 1066785: https://tbpl.mozilla.org/?tree=Ash&rev=3893ea460be3

Yeah, I want this.

Comment on attachment 8492241 [details] [diff] [review] Add action counts to mozlog status handler to account for crashes. Review of attachment 8492241 [details] [diff] [review]: ----------------------------------------------------------------- ::: testing/mozbase/mozlog/mozlog/structured/handlers/statushandler.py @@ +10,4 @@ > from mozlog.structured.structuredlog import log_levels > > +RunSummary = namedtuple("RunSummary", > + ("unexpected", "skipped", "level_counts", "action_counts")) Call level_counts log_level_counts.

Try: https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=b628965801b0