<p dir="ltr"><br>
On Apr 1, 2015 9:29 PM, "Brent Fulgham" <<a href="mailto:bfulgham@apple.com">bfulgham@apple.com</a>> wrote:<br>
><br>
> The Windows EWS bots process patches fairly quickly. Once I corrected the problem today, it managed to process about 97 patches in about an hour.<br>
><br>
> I do think one bottleneck is due to individual EWS bots “locking” patches. The first bot to reach a patch locks the patch against other bots handling it. If the patch happens to be ‘consumed’ be a bot with some kind of problem (e.g., bad local configuration, a full disk drive, etc.), that patch will not be touched again — even if the other eight EWS bots are sitting dormant.</p>
<p dir="ltr">It might be worth adding the ability for a bot to unlock a patch when it detects a problem with itself. We didn't have that originally because we were paranoid about handling the case of an "unclean" bot shutdown and wanted to make sure we got a lot of experience with that case. At this point, it's probably an overly paranoid design.</p>
<p dir="ltr">Adam<br></p>
<p dir="ltr">> Is there some other processing metric you are concerned about?<br>
><br>
> Brent Fulgham - Apple Inc.<br>
><br>
><br>
><br>
>> On Apr 1, 2015, at 2:26 PM, Maciej Stachowiak <<a href="mailto:mjs@apple.com">mjs@apple.com</a>> wrote:<br>
>><br>
>><br>
>> Is it possible to make EWS start processing changes more promptly?<br>
>><br>
>>> On Apr 1, 2015, at 12:42 PM, Brent Fulgham <<a href="mailto:bfulgham@apple.com">bfulgham@apple.com</a>> wrote:<br>
>>><br>
>>> Hi Everyone,<br>
>>><br>
>>> We lost Windows EWS coverage for the past 36 hours due to a very benign-appearing change to some webkitpy code. I haven’t yet figured out why this particular set of changes caused the Windows bots to start failing, but it has to do with various differences between the Cygwin Python 2.7.8 build and the versions used on our other EWS bots.<br>
>>><br>
>>> This does not seem like something developers SHOULD have to worry about, but it’s an unfortunately reality that they really do need to.<br>
>>><br>
>>> To make matters worse, the patch that introduced the problem passed EWS. This is because the EWS bots only really begin using changes to webkitpy when they restart processing (about once every 10-13 build iterations).<br>
>>><br>
>>> To help combat this problem, I’d like to request that when making changes to webkitpy, please keep an eye on the various EWS bots to make sure they continue processing. If they do start failing, please roll the patch back out and we can work together to resolve the issue.<br>
>>><br>
>>> I apologize for how manual and inconvenient this needs to be (at least for now), but keeping the EWS up and running is critical to the smooth function of this project.<br>
>>><br>
>>> If you have any questions, please don’t hesitate to e-mail me or look for me on IRC.<br>
>>><br>
>>> Thanks!<br>
>>><br>
>>> -Brent<br>
>>> _______________________________________________<br>
>>> webkit-dev mailing list<br>
>>> <a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>
>>> <a href="https://lists.webkit.org/mailman/listinfo/webkit-dev">https://lists.webkit.org/mailman/listinfo/webkit-dev</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> webkit-dev mailing list<br>
>> <a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>
>> <a href="https://lists.webkit.org/mailman/listinfo/webkit-dev">https://lists.webkit.org/mailman/listinfo/webkit-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> webkit-dev mailing list<br>
> <a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>
> <a href="https://lists.webkit.org/mailman/listinfo/webkit-dev">https://lists.webkit.org/mailman/listinfo/webkit-dev</a><br>
><br>
</p>