Enable all tryserver tests even when not production master.

Enable all tryserver tests even when not production master.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=207987

[iannucci, 2013-06-22 01:33:02]

lgtm

Ew... is there something we can do to detect this sort of thing in the future?

lgtm

[commit-bot: I haz the power, 2013-06-22 01:33:09]

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

[commit-bot: I haz the power, 2013-06-22 01:33:26]

Change committed as 207987

[M-A Ruel, 2013-07-09 15:36:08]

On 2013/06/22 01:33:02, iannucci wrote:
> lgtm
> 
> Ew... is there something we can do to detect this sort of thing in the future?
> 
> lgtm

It was done on purpose, why is that a problem?

[iannucci, 2013-07-09 16:55:29]

On 2013/07/09 15:36:08, Marc-Antoine Ruel wrote:
> On 2013/06/22 01:33:02, iannucci wrote:
> > lgtm
> > 
> > Ew... is there something we can do to detect this sort of thing in the
future?
> > 
> > lgtm
> 
> It was done on purpose, why is that a problem?

Hardcoding a list of tests which is dependent on the detected hostname of the
machine is not a problem?

[M-A Ruel, 2013-07-09 17:03:29]

> Hardcoding a list of tests which is dependent on the detected hostname of the
> machine is not a problem?

Well, it's important to ensure that the production host runs the right config,
this differentiation makes it very obvious.

I don't know if you test try server changes locally often but I do. And when I
do, this limitation makes it possible to reduce my test cycle time < 5 minutes,
which is primordial to my productivity.

[Mike Stip (use stip instead), 2013-07-09 18:20:49]

This completely breaks buildrunner and all build scanning tools. We need to
limit is_production_host as much as possible.