Handle content_shell failing to start on android as device going offline.

Handle content_shell failing to start on android as device going offline.

This should then take advantage of the new "fault-tolerance" mode in run-webkit-tests and redirect all the tests queued for that device to another one.

Note that this behavior isn't ideal because it's possible content_shell could just be broken (and it's not a device-level issue at all), but this is worth giving a shot.

TBR=ojan@chromium.org, peter@chromium.org
BUG=305040, 306313
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=159466

[Dirk Pranke, 2013-10-11 18:13:24]

TBR'ing since the bot is current hosed because of a device issue, so let's see
what this does.

[Dirk Pranke, 2013-10-11 18:13:48]

Committed patchset #1 manually as r159466 (presubmit successful).

[Dirk Pranke, 2013-10-11 18:19:12]

Also, if this actually turns out to be useful enough to keep, I'll come back to
clean up the code and add a test.

[Peter Beverloo, 2013-10-15 16:40:07]

lgtm

https://codereview.chromium.org/27046003/diff/1/Tools/Scripts/webkitpy/layout...
File Tools/Scripts/webkitpy/layout_tests/controllers/layout_test_runner.py
(right):

https://codereview.chromium.org/27046003/diff/1/Tools/Scripts/webkitpy/layout...
Tools/Scripts/webkitpy/layout_tests/controllers/layout_test_runner.py:245: if
device_offline:
nit: throw a DeviceOffline exception to avoid code duplication with lines
249-253?