Run logcat monitor and device status check on bisect bots.

Run logcat monitor and device status check on bisect bots.

BUG=299782
TBR=ilevy@chromium.org

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

[navabi, 2013-12-06 19:13:57]

https://codereview.chromium.org/108733003/diff/1/build/android/buildbot/bb_ru...
File build/android/buildbot/bb_run_bot.py (right):

https://codereview.chromium.org/108733003/diff/1/build/android/buildbot/bb_ru...
build/android/buildbot/bb_run_bot.py:165: B('perf-bisect-builder-tests-dbg',
H(['bisect_perf_regression']), T([])),
The empty T([]) will make bb_device_steps::MainTestWrapper run, where the device
status check is executed. This will also spawn logcat monitor. Since no other
options are passed, those are the only things that will be added by adding a T.

The bug was to add device status check. Ok if it comes with logcat monitor,
which will print the logcat of the device. Generally, this is good to have
anyway to investigate device issues.

[tonyg, 2013-12-06 19:15:30]

lgtm

[commit-bot: I haz the power, 2013-12-06 20:32:27]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/navabi@google.com/108733003/20001

[commit-bot: I haz the power, 2013-12-07 04:31:20]

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-12-08 20:12:29]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/navabi@google.com/108733003/20001

[commit-bot: I haz the power, 2013-12-08 22:51:20]

Change committed as 239418