mash: Update Mojo ChromiumOS fyi bot config.

mash: Update Mojo ChromiumOS fyi bot config.

Make the Mojo ChromiumOS fyi bot shared/ozone/dcheck.

BUG=639882
TEST=Config matches that requested on the bug.
R=dpranke@chromium.org

Committed: https://crrev.com/10fa24d67b3d7cca19c634a94fe027c5d8692169
Cr-Commit-Position: refs/heads/master@{#413876}

[msw, 2016-08-22 19:09:38]

Hey Dirk, please take a look; thanks!
Am I missing any training scripts or similar?

[Dirk Pranke, 2016-08-22 19:22:15]

Why do you want this to be shared release? That's an unusual configuration.

[msw, 2016-08-22 19:23:16]

Description was changed from

==========
mash: Update Mojo ChromiumOS fyi bot config.

Make the Mojo ChromiumOS fyi bot shared/ozone/dcheck.

BUG=639882
TEST=Config matches that requested on the bug.
R=dpranke@chromium.org
==========

to

==========
mash: Update Mojo ChromiumOS fyi bot config.

Make the Mojo ChromiumOS fyi bot shared/ozone/dcheck.

BUG=639882
TEST=Config matches that requested on the bug.
R=dpranke@chromium.org
==========

[msw, 2016-08-22 19:25:35]

On 2016/08/22 19:22:15, Dirk Pranke wrote:
> Why do you want this to be shared release? That's an unusual configuration.

Sadrul said "there are issues with tcmalloc in non-component builds" on the bug,
and cited a blocking bug for using the static build with Ozone (
http://crbug.com/594674 - Ozone X11 mash_shell static builds crash in tcmalloc).
Perhaps it would make more sense to use a shared debug config until that's 
fixed?

[Dirk Pranke, 2016-08-22 19:40:54]

On 2016/08/22 19:25:35, msw wrote:
> On 2016/08/22 19:22:15, Dirk Pranke wrote:
> > Why do you want this to be shared release? That's an unusual configuration.
> 
> Sadrul said "there are issues with tcmalloc in non-component builds" on the
bug,
> and cited a blocking bug for using the static build with Ozone (
> http://crbug.com/594674 - Ozone X11 mash_shell static builds crash in
tcmalloc).
> Perhaps it would make more sense to use a shared debug config until that's 
> fixed?

I'd either make it a debug config or at least add a comment/TODO with the link
to
the bug, if you'd really rather it be static release.

[msw, 2016-08-22 20:40:53]

I made it debug (dchecks and shared) instead of shared release plus dchecks.
Sadrul, please lmk if that should work for us.

[sadrul, 2016-08-23 01:04:28]

On 2016/08/22 20:40:53, msw wrote:
> I made it debug (dchecks and shared) instead of shared release plus dchecks.
> Sadrul, please lmk if that should work for us.

'debug' config isn't necessary, and I am not sure it would be more useful than
release + dcheck. But it shouldn't be a problem either (other than being slower,
I guess?).

What I am hoping to do with this bot: turn on more browser-tests for
mash_browser_tests in this bot first, and graduate them to the main waterfall
when they are reliably non-flaky. (same for other tests, e.g.
content_browsertests + mus-gpu). Ideally, we would just use the default config
(i.e. [static + release + dcheck]), but that combination has issues with
tcmalloc. so until that is sorted out, I was thinking we could (temporarily)
switch to [component + release + dcheck]. But as mentioned earlier, [component +
debug] would also be OK.

[msw, 2016-08-23 18:17:11]

I added a TODO to restore release+dcheck; citing crbug.com/594674
If it's unbearably slow, we can try shared release plus dchecks.
Dirk, please take a look; thanks!

[Dirk Pranke, 2016-08-23 19:27:55]

lgtm

[msw, 2016-08-23 19:48:38]

The CQ bit was checked by msw@chromium.org

[commit-bot: I haz the power, 2016-08-23 19:49:29]

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-08-23 21:14:09]

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

[commit-bot: I haz the power, 2016-08-23 21:14:10]

Try jobs failed on following builders:
  win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[msw, 2016-08-23 21:38:29]

The CQ bit was checked by msw@chromium.org

[commit-bot: I haz the power, 2016-08-23 21:39:35]

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-08-23 22:50:30]

Description was changed from

==========
mash: Update Mojo ChromiumOS fyi bot config.

Make the Mojo ChromiumOS fyi bot shared/ozone/dcheck.

BUG=639882
TEST=Config matches that requested on the bug.
R=dpranke@chromium.org
==========

to

==========
mash: Update Mojo ChromiumOS fyi bot config.

Make the Mojo ChromiumOS fyi bot shared/ozone/dcheck.

BUG=639882
TEST=Config matches that requested on the bug.
R=dpranke@chromium.org
==========

[commit-bot: I haz the power, 2016-08-23 22:50:33]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-08-23 22:53:03]

Description was changed from

==========
mash: Update Mojo ChromiumOS fyi bot config.

Make the Mojo ChromiumOS fyi bot shared/ozone/dcheck.

BUG=639882
TEST=Config matches that requested on the bug.
R=dpranke@chromium.org
==========

to

==========
mash: Update Mojo ChromiumOS fyi bot config.

Make the Mojo ChromiumOS fyi bot shared/ozone/dcheck.

BUG=639882
TEST=Config matches that requested on the bug.
R=dpranke@chromium.org

Committed: https://crrev.com/10fa24d67b3d7cca19c634a94fe027c5d8692169
Cr-Commit-Position: refs/heads/master@{#413876}
==========

[commit-bot: I haz the power, 2016-08-23 22:53:04]

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