1466102 - when there are bad conditions in a reftest.list file, we emit an error and wait for a timeout, this should terminate the browser/harness

Status: NEW

(Testing :: Reftest, defect, P3)

Description

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

example: 
https://treeherder.mozilla.org/#/jobs?repo=try&revision=6ab38d0e05797049a10561b2a4865244bd9e15d0&filter-searchStr=r1%20android

[task 2018-06-01T11:54:48.551Z] 11:54:48     INFO -  REFTEST ERROR | EXCEPTION: Error in manifest file http://10.0.2.2:8888/tests/layout/reftests/bugs/reftest.list line 308: unknown test type fuzzy-if(Android&&AndroidVersion=='26',3,1512)
[task 2018-06-01T12:01:33.334Z] 12:01:33     INFO -  Browser unexpectedly found running. Killing...
[task 2018-06-01T12:01:33.334Z] 12:01:33     INFO -  REFTEST TEST-INFO | started process screentopng
[task 2018-06-01T12:01:33.696Z] 12:01:33     INFO -  REFTEST TEST-INFO | screentopng: exit 0
[task 2018-06-01T12:01:48.343Z] 12:01:48  WARNING -  TEST-UNEXPECTED-FAIL | remoteautomation.py | application timed out after 370 seconds with no output
[task 2018-06-01T12:01:48.344Z] 12:01:48     INFO -  INFO | automation.py | Application ran for: 0:08:36.286869


another example:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=00df3a8122a8ab22e78c518eb8de80b8bbd6085d&filter-searchStr=qr%20r1%20debug&selectedJob=181253753

00:35:12     INFO -  REFTEST ERROR | EXCEPTION: ReferenceError: invalid assignment left-hand side