Disable chrome target and tests on Windows.

Disable chrome target and tests on Windows.

The bots don't have the capacity to link these targets.

TBR=dpranke

Committed: https://crrev.com/6bb47923233d145ffd17a9d4aa72dfee059e468f
Cr-Commit-Position: refs/heads/master@{#314065}

[brettw, 2015-01-31 07:10:51]

brettw@chromium.org changed reviewers:
+ dpranke@chromium.org

[brettw, 2015-01-31 07:11:41]

The CQ bit was checked by brettw@chromium.org

[commit-bot: I haz the power, 2015-01-31 07:12:51]

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

[commit-bot: I haz the power, 2015-01-31 08:03:50]

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

[commit-bot: I haz the power, 2015-01-31 08:03:51]

Try jobs failed on following builders:
  win8_chromium_gn_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_gn_...)

[Dirk Pranke, 2015-01-31 18:04:52]

On 2015/01/31 08:03:51, I haz the power (commit-bot) wrote:
> Try jobs failed on following builders:
>   win8_chromium_gn_rel on tryserver.chromium.win
>
(http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_gn_...)

Looks like a couple of other targets need to be disabled as well; I've posted a
patch that does this to https://codereview.chromium.org/875123003 .

[Dirk Pranke, 2015-01-31 18:22:08]

On 2015/01/31 18:04:52, Dirk Pranke wrote:
> Looks like a couple of other targets need to be disabled as well; I've posted
a
> patch that does this to https://codereview.chromium.org/875123003 .

I've given up on that patch and will revert the original patch instead:

https://codereview.chromium.org/886243002/

[brettw, 2015-01-31 18:34:29]

The CQ bit was checked by brettw@chromium.org

[commit-bot: I haz the power, 2015-01-31 18:34:57]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/891893002/20001

[Dirk Pranke, 2015-01-31 18:49:47]

On 2015/01/31 18:34:57, I haz the power (commit-bot) wrote:
> CQ is trying da patch. Follow status at
>  https://chromium-cq-status.appspot.com/patch-status/891893002/20001

By the way, I think part of the problem is likely that we have goma disabled on
the win bots at the moment; when we first tried enabling it a few months ago, we
hit a weird bug in goma. I think that bug has been fixed, but we haven't tried
re-enabling it since, so we should try again.

We also don't have precompiled header support, but I think goma doesn't support
precompiled headers, so that may matter less.

There's also the fact that w/ chrome building, we're now building something like
5x the targets that we were a month ago, so we might just be flat-out overloaded
on the system as a whole even w/ goma, but clearly we need to get that working
first.

[commit-bot: I haz the power, 2015-01-31 20:19:05]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-01-31 20:20:05]

Patchset 2 (id:??) landed as
https://crrev.com/6bb47923233d145ffd17a9d4aa72dfee059e468f
Cr-Commit-Position: refs/heads/master@{#314065}