On Thu, Jul 23, 2009 at 5:30 PM, Tony Chang <[email protected]> wrote:

>
> Here's a crappy work around:
> Add a gclient hook that checks for grd file changes.  When a grd file
> changes, force delete the header it would generate.  I'm pretty sure
> this would prevent bad builds from IncrediBuild.
>
> Alternately, maybe we can make a reduced test case and file a bug
> against IncrediBuild.


I think finding and implementing a work-around is the best way to go.  I'm
not an expert on this stuff, but your solution seems like a good one.


>
>
> On Thu, Jul 23, 2009 at 4:44 PM, Paweł Hajdan
> Jr.<[email protected]> wrote:
> > Is it possible to force it to rebuild some files, or... I don't know, do
> you
> > see some real way to fix this problem?
> >
> > On Thu, Jul 23, 2009 at 16:41, Tony Chang <[email protected]> wrote:
> >>
> >> To elaborate on Peter's comment.  IncrediBuild (which the buildbots
> >> use) get confused by changes to our grd files.  Our grd files generate
> >> headers, which should then cause lots of cc files to get rebuilt.
> >> Visual Studio seems to always get this right, but IncrediBuild gets
> >> this wrong and cc files don't get rebuilt.  I imagine IncrediBuild is
> >> checking the timestamp of the file before the headers are re-generated
> >> and doesn't realize it needs to rebuild.
> >>
> >> On Thu, Jul 23, 2009 at 4:38 PM, Peter Kasting<[email protected]>
> wrote:
> >> > On Thu, Jul 23, 2009 at 4:31 PM, Paweł Hajdan Jr.
> >> > <[email protected]>
> >> > wrote:
> >> >>
> >> >> Some of the flaky failures are caused by resource bundle issues. If
> you
> >> >> are familiar with the build process, or the resource bundle, please
> >> >> take a
> >> >> look.
> >> >
> >> > It looks like something needed a manual clobber and didn't get it.
> >> > PK
> >> > >> >
> >> >
> >
> >
>
> >
>

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

Reply via email to