I landed changes to the script and gclient which should make it clobber the
right files. However, I'd prefer to confirm that the failures disappear from
the flakiness dashboard (for a few days).
I got a lot of valid complaints about this script producing cluttering debug
output. I really plan to fix that as soon as I'm sure things are okay. By
that time, you can apply locally http://codereview.chromium.org/164173 (by
sgk). If you're really frustrated, please just send me the output which
shows it clobbers correct files (including chrome, app, and webkit - that's
the important part). That will allow me to remove the debug output
immediately.

On Mon, Aug 3, 2009 at 16:20, Paweł Hajdan Jr. <phajdan...@chromium.org>wrote:

> Oh, there as a problem a while ago on the buildbots. In case you hit that
> in your checkout (MemoryError), just run gclient sync again. Sorry for the
> inconvenience. I'm working on a proper fix.
>
>
> On Mon, Aug 3, 2009 at 16:00, Paweł Hajdan Jr. <phajdan...@chromium.org>wrote:
>
>> In http://src.chromium.org/viewvc/chrome?view=rev&revision=22325 I added
>> a hook (running only on Windows), which clobbers headers generated by grit
>> when grd files are modified. It should workaround an issue with
>> IncrediBuild, and reduce flakiness on the buildbots.
>> Please notify me in case of any problems with the new hook.
>>
>
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to