832594 - test_execute_async_script.py needs to do something other than sit for 7200 seconds in the case of a crash

Status: RESOLVED FIXED

(Remote Protocol :: Marionette, defect)

Description

[Phil Ringnalda (:philor)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=18952503&tree=Mozilla-Inbound 
23:33:01     INFO -  TEST-START test_execute_async_script.py
23:36:01     INFO -  test_check_window (test_execute_async_script.TestExecuteAsyncChrome) ... ERROR
23:39:01     INFO -  test_execute_async_js_exception (test_execute_async_script.TestExecuteAsyncChrome) ... ERROR
23:42:01     INFO -  test_execute_async_ours (test_execute_async_script.TestExecuteAsyncChrome) ... ERROR
23:45:02     INFO -  test_execute_async_simple (test_execute_async_script.TestExecuteAsyncChrome) ... ERROR
23:48:02     INFO -  test_execute_async_timeout (test_execute_async_script.TestExecuteAsyncChrome) ... ERROR
23:51:02     INFO -  test_execute_async_unload (test_execute_async_script.TestExecuteAsyncChrome) ... ERROR
23:54:02     INFO -  test_execute_js_exception (test_execute_async_script.TestExecuteAsyncChrome) ... ERROR

command timed out: 7200 seconds elapsed, attempting to kill

https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=7dbbb6e3d240 hit a fatal assertion at startup. In the case of the other test suites, that burned around 3 minutes of machine time per suite. In the case of marionette, it burned 2 hours per platform - the tests before test_execute_async_script.py blew up just fine, and then that test sat until buildbot timed it out after 2 hours with no output.

Comment 1

[Jonathan Griffin (:jgriffin)]

We now timeout after 1000s with no output.