Open Bug 1466102 Opened 6 years ago Updated 2 years ago

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


(Testing :: Reftest, defect, P3)



(Not tracked)


(Reporter: jmaher, Unassigned)



[task 2018-06-01T11:54:48.551Z] 11:54:48     INFO -  REFTEST ERROR | EXCEPTION: Error in manifest file 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 | | application timed out after 370 seconds with no output
[task 2018-06-01T12:01:48.344Z] 12:01:48     INFO -  INFO | | Application ran for: 0:08:36.286869

another example:

00:35:12     INFO -  REFTEST ERROR | EXCEPTION: ReferenceError: invalid assignment left-hand side
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.