Re-enable android bisect bot for Perf CQ jobs.

Re-enable android bisect bot for Perf CQ jobs.

BUG=568661
Committed: https://crrev.com/95e79fa896e6bf222e17e3a1f42f713d57a12430
Cr-Commit-Position: refs/heads/master@{#371830}

[prasadv, 2016-01-27 17:31:38]

prasadv@chromium.org changed reviewers:
+ dtu@chromium.org, sullivan@chromium.org

[sullivan, 2016-01-27 17:36:31]

The CQ bit was checked by sullivan@chromium.org

[sullivan, 2016-01-27 17:36:31]

lgtm

Any thoughts on how we can
1) Remember to disable things before scheduled outages and as soon as we know
about unplanned outages
2) Remember to re-enable after known outages?

[commit-bot: I haz the power, 2016-01-27 17:37:17]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1641713003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1641713003/1

[prasadv, 2016-01-27 17:42:34]

On 2016/01/27 17:36:31, sullivan wrote:
> lgtm
> 
> Any thoughts on how we can
> 1) Remember to disable things before scheduled outages and as soon as we know
> about unplanned outages
> 2) Remember to re-enable after known outages?

On possible way is to create a bug to re-enable (block on issue caused disable)
and assigning it to self when we disable things.

[commit-bot: I haz the power, 2016-01-27 18:50:09]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-01-27 18:51:31]

Description was changed from

==========
Re-enable android bisect bot for Perf CQ jobs.

BUG=568661
==========

to

==========
Re-enable android bisect bot for Perf CQ jobs.

BUG=568661

Committed: https://crrev.com/95e79fa896e6bf222e17e3a1f42f713d57a12430
Cr-Commit-Position: refs/heads/master@{#371830}
==========

[commit-bot: I haz the power, 2016-01-27 18:51:32]

Patchset 1 (id:??) landed as
https://crrev.com/95e79fa896e6bf222e17e3a1f42f713d57a12430
Cr-Commit-Position: refs/heads/master@{#371830}