Turn on linux_chromium_headless_dbg CQ builder at 10%

Turn on linux_chromium_headless_dbg CQ builder at 10%

BUG=632008
Committed: https://crrev.com/eefe833ae27a644a219eb0d4b047ff2e3aee7c0d
Cr-Commit-Position: refs/heads/master@{#430906}

[perezju, 2016-09-16 16:02:26]

perezju@chromium.org changed reviewers:
+ phajdan.jr@chromium.org

[Paweł Hajdan Jr., 2016-09-16 17:47:33]

phajdan.jr@chromium.org changed reviewers:
+ jam@chromium.org

[Paweł Hajdan Jr., 2016-09-16 17:47:33]

+jam

Has this been reviewed by chrome-eng-review?

[jam, 2016-09-16 20:04:58]

On 2016/09/16 17:47:33, Paweł Hajdan Jr. wrote:
> +jam
> 
> Has this been reviewed by chrome-eng-review?

I haven't heard of it.

Can infra team do the due diligence on the capacity and speed of this?

There are only two runs and they both failed. Why does the compile not finish in
two hours? Even for a clobber on other builders it doesn't take that long.

Will this have tests?

[Paweł Hajdan Jr., 2016-09-19 23:22:23]

On 2016/09/16 at 20:04:58, jam wrote:
> On 2016/09/16 17:47:33, Paweł Hajdan Jr. wrote:
> > +jam
> > 
> > Has this been reviewed by chrome-eng-review?
> 
> I haven't heard of it.
> 
> Can infra team do the due diligence on the capacity and speed of this?

We'll need to proceed with at least this CL to gather enough data for that.

My point was it may not be worth it unless chrome-eng-review is OK with this
config on main waterfall and CQ. I think we do have cycle time data for the FYI
builder mentioned in the bug.

[perezju, 2016-09-22 14:18:41]

On 2016/09/19 23:22:23, Paweł Hajdan Jr. wrote:
> On 2016/09/16 at 20:04:58, jam wrote:
> > On 2016/09/16 17:47:33, Paweł Hajdan Jr. wrote:
> > > +jam
> > > 
> > > Has this been reviewed by chrome-eng-review?
> > 
> > I haven't heard of it.
> > 
> > Can infra team do the due diligence on the capacity and speed of this?
> 
> We'll need to proceed with at least this CL to gather enough data for that.
> 
> My point was it may not be worth it unless chrome-eng-review is OK with this
> config on main waterfall and CQ. I think we do have cycle time data for the
FYI
> builder mentioned in the bug.

It wasn't quite clear to us exactly when was it needed to email
chrome-eng-review (i.e. before or after setting up the experiment in CQ to
assess capacity and speed). I hope to compose and send an email soon, but I also
want to investigate a bit further about the long compilation time.

[perezju, 2016-10-25 08:52:25]

Paweł, PTAL.

Thanks!

[Paweł Hajdan Jr., 2016-10-25 18:12:47]

LGTM

Please make sure to update commit message (replace dbg with rel).

[jam, 2016-10-25 19:16:21]

lgtm

[perezju, 2016-11-09 09:46:33]

The CQ bit was checked by perezju@chromium.org

[commit-bot: I haz the power, 2016-11-09 09:46:40]

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-11-09 09:55:30]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-11-09 09:58:26]

Description was changed from

==========
Turn on linux_chromium_headless_dbg CQ builder at 10%

BUG=632008
==========

to

==========
Turn on linux_chromium_headless_dbg CQ builder at 10%

BUG=632008

Committed: https://crrev.com/eefe833ae27a644a219eb0d4b047ff2e3aee7c0d
Cr-Commit-Position: refs/heads/master@{#430906}
==========

[commit-bot: I haz the power, 2016-11-09 09:58:26]

Patchset 3 (id:??) landed as
https://crrev.com/eefe833ae27a644a219eb0d4b047ff2e3aee7c0d
Cr-Commit-Position: refs/heads/master@{#430906}