Closed Bug 1024416 Opened 11 years ago Closed 9 years ago

Make Marionette handle the hangs/crashes in bug 1023151 so as to not hit the buildbot timeout

Categories

(Remote Protocol :: Marionette, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: emorley, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: pi-marionette-runner, Whiteboard: [affects=marionette])

Broken out from bug 1023151: (In reply to Ed Morley [:edmorley UTC+0] from bug 1023151 comment #5) > (In reply to David Burns :automatedtester from comment #4) > > I suspect that there was an issue in marionette that caused it to crash. The > > timeoutexception tends to be raised from the browser. > > > > I tried to load the log but couldnt see anything useful being output about > > what the cause could be > > Please can we make the harness catch cases where Marionette has crashed and > nothing was output? > > ie: > > Actual: > { > 15:05:27 INFO - test_sandbox_reuse > (test_execute_script.TestExecuteContent) ... ERROR > 15:11:30 INFO - test_stack_trace > (test_execute_script.TestExecuteContent) ... ERROR > > command timed out: 7200 seconds elapsed, attempting to kill > } > > Expected: > { > 15:05:27 INFO - test_sandbox_reuse > (test_execute_script.TestExecuteContent) ... ERROR > 15:11:30 INFO - test_stack_trace > (test_execute_script.TestExecuteContent) ... ERROR > 15:16:30 ERROR - TEST-UNEXPECTED-FAIL | test_execute_script.py | > application timed out after 330 seconds with no output > } > (or something of that form, similar to mochitest etc)
Whiteboard: [affects=marionette]
Lots of the harness has been made more robust and we have not hit this issue in a long time so going to assume we have fixed it.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.