Turn off cygwin for grit again.

Turn off cygwin for grit again.
Roll gyp has already been updated prevent the issues which happened previously with msvs 2008.

This is a second attempt at https://chromiumcodereview.appspot.com/10832121/
BUG=123026
R=scottmg,joi,thakis


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

[iannucci, 2012-08-11 00:25:58]

Ok. So I ran this through win_rel (noclobber) and win_rel (clobber).
Interestingly, the clobber build worked.

I'm running another clobber build to be sure. "Nuke it from orbit", and all
that.

Or, do you (@scottmg) think this behavior might be indicative of a deeper issue?

Rob

[scottmg, 2012-08-11 00:29:59]

On 2012/08/11 00:25:58, iannucci wrote:
> Ok. So I ran this through win_rel (noclobber) and win_rel (clobber).
> Interestingly, the clobber build worked.

Did the noclobber work? Or it failed for some reason?

Otherwise lgtm. I'm going to have to shut down my machines pretty soon so I
won't be able to watch it if you commit now. Maybe Monday morning?

[iannucci, 2012-08-11 00:31:59]

On 2012/08/11 00:29:59, scottmg wrote:
> On 2012/08/11 00:25:58, iannucci wrote:
> > Ok. So I ran this through win_rel (noclobber) and win_rel (clobber).
> > Interestingly, the clobber build worked.
> 
> Did the noclobber work? Or it failed for some reason?
> 
> Otherwise lgtm. I'm going to have to shut down my machines pretty soon so I
> won't be able to watch it if you commit now. Maybe Monday morning?

No the noclobber failed with the old error.

Yeah I have to shut my machines off soon too :). I'll do this early monday.

[iannucci, 2012-08-11 00:38:36]

On 2012/08/11 00:31:59, iannucci wrote:
> On 2012/08/11 00:29:59, scottmg wrote:
> > On 2012/08/11 00:25:58, iannucci wrote:
> > > Ok. So I ran this through win_rel (noclobber) and win_rel (clobber).
> > > Interestingly, the clobber build worked.
> > 
> > Did the noclobber work? Or it failed for some reason?
> > 
> > Otherwise lgtm. I'm going to have to shut down my machines pretty soon so I
> > won't be able to watch it if you commit now. Maybe Monday morning?
> 
> No the noclobber failed with the old error.
> 
> Yeah I have to shut my machines off soon too :). I'll do this early monday.

Whoa... the second clobber build failed. There's definitely something More
Sinister going on. I'll look into it monday.

[iannucci, 2012-08-11 01:58:53]

On 2012/08/11 00:38:36, iannucci wrote:
> On 2012/08/11 00:31:59, iannucci wrote:
> > On 2012/08/11 00:29:59, scottmg wrote:
> > > On 2012/08/11 00:25:58, iannucci wrote:
> > > > Ok. So I ran this through win_rel (noclobber) and win_rel (clobber).
> > > > Interestingly, the clobber build worked.
> > > 
> > > Did the noclobber work? Or it failed for some reason?
> > > 
> > > Otherwise lgtm. I'm going to have to shut down my machines pretty soon so
I
> > > won't be able to watch it if you commit now. Maybe Monday morning?
> > 
> > No the noclobber failed with the old error.
> > 
> > Yeah I have to shut my machines off soon too :). I'll do this early monday.
> 
> Whoa... the second clobber build failed. There's definitely something More
> Sinister going on. I'll look into it monday.

Ah... The non-clobber build was the only one to succeed. This is definitely a
dependency issue (i.e. repack_locales should be totally dependent on
chrome_strings, but that doesn't seem to be the case in the clobber builds).
This should be pretty easy to fix... on monday :)

[iannucci, 2012-08-21 18:28:07]

PTAL again: If you agree that the fails aren't due to the change, I'll add it as
notry :)

[scottmg, 2012-08-21 18:35:10]

On 2012/08/21 18:28:07, iannucci wrote:
> PTAL again: If you agree that the fails aren't due to the change, I'll add it
as
> notry :)

Don't look related to me. I normally just re-check and let the CQ try a few
times.

[joi, 2012-08-21 19:22:54]

They don't look related but I would also suggest just pulling the CQ
trigger again.

Cheers,
Jói


On Tue, Aug 21, 2012 at 6:35 PM,  <scottmg@chromium.org> wrote:
> On 2012/08/21 18:28:07, iannucci wrote:
>>
>> PTAL again: If you agree that the fails aren't due to the change, I'll add
>> it
>
> as
>>
>> notry :)
>
>
> Don't look related to me. I normally just re-check and let the CQ try a few
> times.
>
> http://codereview.chromium.org/10824268/

[commit-bot: I haz the power, 2012-08-21 19:53:02]

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

[commit-bot: I haz the power, 2012-08-21 21:25:43]

Change committed as 152639