843761 - B2G mochitests shouldn't abort the test run if a single test times out

Status: RESOLVED WONTFIX

(Testing :: Mochitest, defect)

Description

[Andrew Halberstadt [:ahal]]

I noticed that when a test times out, the run gets aborted even though subsequent tests are still running. For example, look at:
https://tbpl.mozilla.org/php/getParsedLog.php?id=19956010&tree=Cedar

In the normal part of the log (non-logcat part) we see:

> 09:23:11  WARNING -  TEST-UNEXPECTED-FAIL | /tests/dom/encoding/test/test_stringencoding.html | application timed out after 330 seconds with no output
> 09:23:11  WARNING -  This is a harness error.
> 09:23:11     INFO -  INFO | automation.py | Application ran for: 0:11:06.151349
> 09:23:11     INFO -  INFO | automation.py | Reading PID log: /tmp/tmpmNFfmzpidlog
> 09:24:14     INFO -  WARNING | automationutils.processLeakLog() | refcount logging is off, so leaks can't be detected!
> 09:24:14     INFO -  INFO | runtests.py | Running tests: end.

However if you look at the logcat part, you see that the tests continue running on the device afterwards, even though the python side has decided to abort. We should avoid aborting if we don't need to.