Revert of Redo test after step failure if multiple android devices are connected to lin…

Revert of Redo test after step failure if multiple android devices are connected to lin… (patchset #12 id:220001 of https://codereview.chromium.org/2045043002/ )

Reason for revert:
Broke bisect jobs,
android_chromium.api.devices() should be changed to 
android_chromium.api.devices

Original issue's description:
> Right now, when an android device connected to a bisect linux host goes offline, 
> we still send bisects to that host, and the bisects fail. 
> So the device needs to be fixed with extremely urgent priority. 
> This CL aims to allow multiple devices to be connected to a linux host and if a device failed, 
> the job would be retried with a device that is still working. 
> 
> BUG=
> 
> Committed: https://chromium.googlesource.com/chromium/tools/build/+/ad6bb0da9b1a53daae0f47c8d806ffe988c46415

TBR=robertocn@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=

Committed: https://chromium.googlesource.com/chromium/tools/build/+/aa1c49f3de8457745402a466c6f29ac83c2a8268

[Ziqi Xiong, 2016-06-30 17:29:35]

The CQ bit was checked by zxiong@google.com

[Ziqi Xiong, 2016-06-30 17:29:35]

Created Revert of Redo test after step failure if multiple android devices are
connected to lin…

[commit-bot: I haz the power, 2016-06-30 17:29:38]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-06-30 17:29:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-06-30 17:29:39]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
Committers are members of the group "project-infra-committers".
Note that this has nothing to do with OWNERS files.

[RobertoCN, 2016-06-30 18:06:20]

The CQ bit was checked by robertocn@chromium.org

[RobertoCN, 2016-06-30 18:06:21]

lgtm

[commit-bot: I haz the power, 2016-06-30 18:06:27]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-06-30 18:10:25]

Description was changed from

==========
Revert of Redo test after step failure if multiple android devices are connected
to lin… (patchset #12 id:220001 of https://codereview.chromium.org/2045043002/ )

Reason for revert:
Broke bisect jobs,
android_chromium.api.devices() should be changed to 
android_chromium.api.devices

Original issue's description:
> Right now, when an android device connected to a bisect linux host goes
offline, 
> we still send bisects to that host, and the bisects fail. 
> So the device needs to be fixed with extremely urgent priority. 
> This CL aims to allow multiple devices to be connected to a linux host and if
a device failed, 
> the job would be retried with a device that is still working. 
> 
> BUG=
> 
> Committed:
https://chromium.googlesource.com/chromium/tools/build/+/ad6bb0da9b1a53daae0f...

TBR=robertocn@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=
==========

to

==========
Revert of Redo test after step failure if multiple android devices are connected
to lin… (patchset #12 id:220001 of https://codereview.chromium.org/2045043002/ )

Reason for revert:
Broke bisect jobs,
android_chromium.api.devices() should be changed to 
android_chromium.api.devices

Original issue's description:
> Right now, when an android device connected to a bisect linux host goes
offline, 
> we still send bisects to that host, and the bisects fail. 
> So the device needs to be fixed with extremely urgent priority. 
> This CL aims to allow multiple devices to be connected to a linux host and if
a device failed, 
> the job would be retried with a device that is still working. 
> 
> BUG=
> 
> Committed:
https://chromium.googlesource.com/chromium/tools/build/+/ad6bb0da9b1a53daae0f...

TBR=robertocn@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=

Committed:
https://chromium.googlesource.com/chromium/tools/build/+/aa1c49f3de8457745402...
==========

[commit-bot: I haz the power, 2016-06-30 18:10:26]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/tools/build/+/aa1c49f3de8457745402...

[nednguyen, 2016-07-07 20:57:11]

On 2016/06/30 18:10:26, commit-bot: I haz the power wrote:
> Committed patchset #1 (id:1) as
>
https://chromium.googlesource.com/chromium/tools/build/+/aa1c49f3de8457745402...

Please add test that would catch the problem when you reland.