Android: Propagate timeouts when sharding(and retrying) tests.

Android: Propagate timeouts when sharding(and retrying) tests.

We use TestResult.GetAllBroken to identify and retry tests.
However, this list is empty if a test times out (and the device is
responsive). In this case we should propagate the timed_out info to the
final result, which will report a STEP_FAILURE based on this
information.

Ex. bad run:
http://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/6093/steps/sandbox_linux_unittests/logs/stdio

BUG=169064
NOTRY=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=175982

[frankf, 2013-01-09 22:11:27]

https://codereview.chromium.org/11833017/diff/1/build/android/pylib/base_test...
File build/android/pylib/base_test_sharder.py (right):

https://codereview.chromium.org/11833017/diff/1/build/android/pylib/base_test...
build/android/pylib/base_test_sharder.py:144: self.tests += [t.name]
@Craig: Lines 133-143 are completely breaking the encapsulation of TestResults
objects and making the code unreadable. I don't mind this hack going in for now,
but we need to refactor this soon.

[Isaac (away), 2013-01-09 22:24:56]

Agree w/ frankf.  This is a hack, but the encapsulation was already broken.

Sounds like he's not too opposed so I'm going to lgtm it.

[commit-bot: I haz the power, 2013-01-09 23:00:00]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/nileshagrawal@chromium.org/11833017/1

[commit-bot: I haz the power, 2013-01-10 01:44:03]

Commit queue rejected this change because the description was changed
between the time the change entered the commit queue and the time it
was ready to commit. You can safely check the commit box again.

[commit-bot: I haz the power, 2013-01-10 01:45:58]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/nileshagrawal@chromium.org/11833017/1

[commit-bot: I haz the power, 2013-01-10 02:05:38]

Change committed as 175982