Bisect config params should alway be empty.

Bisect config params should alway be empty.

BUG=
NOTRY=true

Committed: https://crrev.com/6017d60fc4bfdf6ffb56f66aff105d23cb53b992
Cr-Commit-Position: refs/heads/master@{#293307}

[prasadv, 2014-09-04 16:20:48]

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

[sullivan, 2014-09-04 16:21:36]

The CQ bit was checked by sullivan@chromium.org

[sullivan, 2014-09-04 16:21:37]

lgtm

[qyearsley, 2014-09-04 16:22:06]

On 2014/09/04 16:21:37, sullivan wrote:
> lgtm

lgtm

[qyearsley, 2014-09-04 16:22:21]

The CQ bit was unchecked by qyearsley@chromium.org

[qyearsley, 2014-09-04 16:22:22]

The CQ bit was checked by qyearsley@chromium.org

[commit-bot: I haz the power, 2014-09-04 16:22:35]

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

[commit-bot: I haz the power, 2014-09-04 16:24:49]

Committed patchset #1 (id:1) as 454c8155d781b8901fec9cd6f2503f03ed4c4bce

[tonyg, 2014-09-04 16:27:57]

Didn't we have a PRESUBMIT that verified this at one point in time?

[qyearsley, 2014-09-04 16:30:09]

On 2014/09/04 16:27:57, tonyg wrote:
> Didn't we have a PRESUBMIT that verified this at one point in time?

We do -- I bypassed it when running "git cl upload" in order to get it into the
CL before running "git cl try...", then I forgot about it. Then when I checked
the commit box, it was committed. (BTW, is there another way that I should be
trying bisect jobs with bisect changes without adding a config to the CL?)

[commit-bot: I haz the power, 2014-09-10 03:31:45]

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