Even if cc files aren't getting touched, the app does re-link, which is non-trivial in nature. I see that reproduced on my local tree.
Hrm, if this isn't the issue, what changed last week or so to cause the massive slowdown? On Tue, Apr 28, 2009 at 12:48 PM, Tony Chang <[email protected]> wrote: > I'm not sure this is related to the mac try servers being slow. This > only causes GRIT to re-run (maybe 10s to run on all files?), but > prevents .cc files from being recompiled. > > Mike is right that it causes null builds to be slower. > > I'm happy to rollback, it doesn't matter either way for me, but if > we're trying to speed up the mac try slaves, this probably isn't going > to help (this change has been in for almost a month). > > tony > > On Tue, Apr 28, 2009 at 8:46 AM, Mike Pinkerton <[email protected]> > wrote: >> Yes, this is certainly a direct cause of making a "null build" on mac >> take far, far longer than it should. >> >> Can we just back out Tony's change that was made in the rules to go >> back to the way things were in the short term? >> >> On Tue, Apr 28, 2009 at 11:31 AM, Marc-Antoine Ruel <[email protected]> >> wrote: >>> >>> You really should take a look ASAP because yesterday, the mac try >>> slaves were like 35+ jobs being. That makes mac testing inexistent and >>> will just cause more mac breakage. I assume today, tomorrow, etc will >>> be as bad. >> >> -- >> Mike Pinkerton >> Mac Weenie >> [email protected] >> > -- Mike Pinkerton Mac Weenie [email protected] --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
