1414949 - test view should account for harness level failures

Status: RESOLVED INVALID

(Tree Management Graveyard :: Treeherder: Test-based View, enhancement, P3)

Description

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

right now testview only supports structured logs, unfortunately a harness timeout doesn't yield a structured log:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=7c84d5c721a130d13a143972547860ba3e62aecd&selectedJob=142039334

what can we do here:
1) investigate structured logs from our harnesses
2) support raw log ingestion for test view

Comment 1

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

I think possibly #1 could be doable if we spent the time combing through the in-browser and python harnesses.

:ahal, do you think it is possible to emit structured logs for our test harnesses?

Comment 2

[Andrew Halberstadt [:ahal]]

It is in the structured log already (search for "Application timed out"):
https://public-artifacts.taskcluster.net/E40lgOEiRKG551HuYmT3TQ/0/public/test_info/chrome_raw.log

But it's being logged as an INFO message for some reason:
https://dxr.mozilla.org/mozilla-central/source/testing/mochitest/runtests.py#2763

The next line gets logged as an ERROR though, is that not being picked up either? If not then maybe the test view is only catching actual test failures and not error logs?

Comment 4

[Cameron Dawson [:camd]]

This feature has been removed.