Example: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/151359571-chromeos-test/chromeos4-row9-rack11-host12/

In particular, this is a problem with arc tests -- they install APKs on the android device in ArcTest.initialize()
frequently (at least this week), this takes too long, and is aborted after an hour (I need to see what exactly is aborting the initialize call). This happens separately from the job abort.

Somehow, this results in the server side autoserv regaining control and continuing as if the client test passed.

Finally, parse comes along and spews some cryptic message about wrong indentation while parsing the client logs.


There are multiple problems with this:
- We end up with an aborted test. We should have a failing test.
- autoserv logs are confusing, do not even contain any failure messages.
- we're depending on (according to me) a bug in parsing to not outright pass the test -- parsing is so stupid that it depends and breaks based on indentation. This has caused headaches in the past. Someone can come along and fix this headache. (I tried once). Then, we'll start passing these obviously failing jobs.