Roll gyp r1651:1652.

Roll gyp r1651:1652.

r1652 | iannucci@chromium.org | 2013-06-21 13:55:25 -0700 (Fri, 21 Jun 2013) | 7 linesMake the ninja pool math correct.R=scottmg@chromium.orgBUG=Review URL: https://codereview.chromium.org/17087010

R=scottmg@chromium.org
BUG=

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=208062

[scottmg, 2013-06-21 21:01:48]

lgtm

[commit-bot: I haz the power, 2013-06-21 21:09:37]

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

[commit-bot: I haz the power, 2013-06-21 22:42:45]

Retried try job too often on win_rel for step(s) browser_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[commit-bot: I haz the power, 2013-06-21 23:01:56]

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

[commit-bot: I haz the power, 2013-06-22 02:32:41]

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

[commit-bot: I haz the power, 2013-06-22 03:00:09]

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

[commit-bot: I haz the power, 2013-06-22 03:30:29]

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

[commit-bot: I haz the power, 2013-06-22 13:54:43]

Sorry for I got bad news for ya.
Compile failed with a clobber build on win_x64_rel.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_x64_re...
Your code is likely broken or HEAD is junk. Please ensure your
code is not broken then alert the build sheriffs.
Look at the try server FAQ for more details.

[commit-bot: I haz the power, 2013-06-22 16:19:58]

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

[scottmg, 2013-06-22 16:32:50]

win_rel is one sad panda, cq ftw

[iannucci, 2013-06-22 16:34:02]

On 2013/06/22 16:32:50, scottmg wrote:
> win_rel is one sad panda, cq ftw

Yeah I know.... I'm guessing getting an ICE isn't related from linking too much?

[scottmg, 2013-06-22 16:39:24]

On 2013/06/22 16:34:02, iannucci wrote:
> On 2013/06/22 16:32:50, scottmg wrote:
> > win_rel is one sad panda, cq ftw
> 
> Yeah I know.... I'm guessing getting an ICE isn't related from linking too
much?

I guess it's possible it's caused by oom :/ x86 toolchain normally does say
something along those lines when it's actually out of memory but possibly just
crashes on some code paths (or the x64 toolchain isn't quite so robust to oom).

I find it somewhat hard to believe 4G isn't enough though? Maybe check what the
pool size actually is on the bot to make sure that code is working properly? I
get 15 locally which is right. Maybe we should conservatively go up to 8? z620s
would still get 7-8 concurrent which is fine anyway.

[commit-bot: I haz the power, 2013-06-22 16:48:21]

Change committed as 208062