Android: run bb_device_status_check prior to other steps.

Android: run bb_device_status_check prior to other steps.

This will make sheriffing easier and print the link to the bug
in case there are no online devices.

BUG=324744
TBR=navabi@chromium.org

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

[bulach, 2013-12-02 10:53:22]

no idea if this order was intentional, but I think the "status check" should be
one of the first things to run.. wdyt?

[navabi, 2013-12-02 20:10:40]

This lgtm. This weekend I started looking at the different provisioning scripts
we have. The one that is being called here doesn't do much. For most bots, it
just restarts the devices. For the webkit bots, it installs the
adb_reboot_on_disconnect on the phone, starts it and starts a background process
on the host to provide the heartbeat.

So right now, I see no problem switching the order of those two steps. I may be
adding things this week to the provision script (e.g. dim screen, enable/disable
wifi). I don't anticipate anything I do will require switching back the order.

[bulach, 2013-12-03 09:33:51]

thanks for the detailed explanation armand! CQing..

[commit-bot: I haz the power, 2013-12-03 10:42:53]

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

[commit-bot: I haz the power, 2013-12-03 11:26:23]

Retried try job too often on chromium_presubmit for step(s) presubmit
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=chromium_p...

[commit-bot: I haz the power, 2013-12-03 14:09:10]

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

[commit-bot: I haz the power, 2013-12-03 16:13:37]

Change committed as 238407