We believe all of the EWS bots are back and have (barely) enough
capacity to keep up with the project.
Port maintainers interested in setting up another ews instance for
their port (to help make sure no one breaks it!) need only look at:
WebKitTools/EWSTools/start-queue.sh
Basically starting another EWS instance is as easy as running
webkit-patch win-ews (or gtk-ews, qt-ews, or whatever your port is).
Eventually I may put up a wiki page on the subject.
-eric
On Sun, Oct 24, 2010 at 8:53 AM, Eric Seidel e...@webkit.org wrote:
The EWS bots are mostly back.
The win-ews bot is getting stuck on SVN locks every time it runs...
Something to do with my recent CYGWIN upgrade on that machine I think.
I may need to get a windows person to look at the bot (ping me if
you're interested).
The gtk-ews and cr-linux-ews bots may need more capacity to keep up
with our 200-patch-a-day rate.
The rest of the bots seem fine for now.
I'll update webkit-dev when the rest are back online.
-eric
On Fri, Oct 22, 2010 at 11:11 AM, Eric Seidel e...@webkit.org wrote:
We made it so that the EWS system will always process a patch if it
*ever* saw it with an r?. This means the EWS now will process r+
patches.
However, this is currently more capacity than the current EWS bots can
handle, so they're very back-logged at the moment.
There are several fixes we can make to the EWS system to make it
handle its limited capacity smarter. I'm working on a couple now.
Those interested can follow
https://bugs.webkit.org/show_bug.cgi?id=35460 where I will relate any
fixes to.
I expect to have this all cleaned up by monday.
-eric
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
