dglazkov at chromium.org
Sun Dec 5 10:58:39 PST 2010
That's what happens when you let non-build-people do build-people work :)
On Sun, Dec 5, 2010 at 10:20 AM, Marc-Antoine Ruel <maruel at chromium.org> wrote:
> You need to use --force on automated testing. We didn't have to clobber any
> Le 5 décembre 2010 12:57, Adam Barth <abarth at webkit.org> a écrit :
>> maruel mentioned something about command-line flags we can pass to
>> gclient to make it more robust.
>> On Sun, Dec 5, 2010 at 9:49 AM, Dimitri Glazkov <dglazkov at chromium.org>
>> > You need to rm -rf /Projects/CrMacEWS/WebKit/chromium/third_party. We
>> > had to do the same for build.webkit.org builders this week.
>> > You're right, the dependency management -- the underlying cause of all
>> > cr-specific build pain -- has gotten pretty hairy.
>> > :DG<
>> > On Sat, Dec 4, 2010 at 5:39 PM, Eric Seidel <eric at webkit.org> wrote:
>> >> Has been broken for days.
>> >> http://queues.webkit.org/queue-status/cr-mac-ews
>> >> Any thoughts from Chromium peeps how it's supposed to be fixed? We
>> >> seem to
>> >> be having increasing trouble keeping the Cr EWS bots running w/o
>> >> hand-holding.
>> >> -eric
>> >> _______________________________________________
>> >> webkit-dev mailing list
>> >> webkit-dev at lists.webkit.org
>> >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>> > _______________________________________________
>> > webkit-dev mailing list
>> > webkit-dev at lists.webkit.org
>> > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
More information about the webkit-dev