repost from right account... ---------- Forwarded message ---------- Date: Tue, Dec 1, 2009 at 10:50 AM Subject: Re: [chromium-dev] Where buildbot outputs the intermediate builds? To: robj.pe...@gmail.com Cc: Chromium-dev <chromium-dev@googlegroups.com>
On Tue, Dec 1, 2009 at 10:27 AM, Roberto <robj.pe...@gmail.com> wrote: > Are the buildbots archiving the intermediate builds before building > the final executable? > > If they do, where are they saving them? are they available to > download? > I don't believe we save all of them, some might get included in what is liked to off the waterfall. > If they don't, it would be pretty good if the "masters of buildbots" > could assist in this topic :) > > As we talked in this thread: > > > http://groups.google.com/group/chromium-dev/browse_thread/thread/301e4963629ce6bb/03e5d21c77d6f9a1#03e5d21c77d6f9a1 > > It would be quite useful in order to avoid the first big and time- > consuming build. > So the first issue is probably disk space it would take, especially for debug bits, we would quickly chew through a *lot* of disk space. I haven't looked, but how many platform end up with full paths on debug symbols? ie-would they even work? > I want to give a try to the possibility of incorporating to the first > check out the built libraries for each module. > If it works, the next point would be to modify gclient in order to > automatically checkout this built libraries as well. > > So we'd need to have built libraries for just about every possible revision as a checkout point? Even the build bots don't always do that as their cycling can result in a few cls being lumped together for a given spin. The other trick would be to make sure the process by which they get dropped on the local machine works for timestamps with different timezones to make sure it really doesn't rebuild things. The catch is if you have a local edit, and you last changed it before the sync would the built libraries have newer timestamps (because the bot happened to cycle in time), you'd actually want to make sure you get rebuilds for that case. So off the cuff, this sounds like it could be a win, but when weighted against the work it would take and how often it might not find said bits, I'm not so sure. The existing work on the webkit api so that could become a binary we use, is more limited, but seems like it might be a more attainable win. TVL > Thanks :) > > Roberto. > > > -- > Chromium Developers mailing list: chromium-dev@googlegroups.com > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-dev > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
