Re: [webkit-dev] Leopard Debug
On Feb 24, 2011, at 12:59 AM, Adam Barth wrote: As far I as I can tell, Leopard Debug is not consistently green: http://build.webkit.org/waterfall?show=Leopard%20Intel%20Debug%20(Build) In fact, it's been failing to build much more often than not for an extended period of time (i.e., several weeks). Based on these observations, it should not be a core builder. We can add it back to the set of core builders when it's consistently green again. To be concrete, shall we say building cleanly for a week? Sure, that sounds fine. When I added it back to the core list I expected it to stay green indefinitely, but clearly that was incorrect. Apparently WebCore just keeps growing! Sorry for the trouble. -Adam ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Leopard Debug
As far I as I can tell, Leopard Debug is not consistently green: http://build.webkit.org/waterfall?show=Leopard%20Intel%20Debug%20(Build) In fact, it's been failing to build much more often than not for an extended period of time (i.e., several weeks). Based on these observations, it should not be a core builder. We can add it back to the set of core builders when it's consistently green again. To be concrete, shall we say building cleanly for a week? Adam ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Leopard Debug and Windows Debug test bots are too slow
Hi, It came to my attention that Leopard Debug (Tests) and Windows Debug (Test) are always behind by a significant amount (5-10 hours). Since Leopard and Windows are two major platforms we support, I would like to know when my patch broke these two platforms. However, because these two bots are 5-10 hours behind, it's really hard for me to realize any brokerage I caused or follow up later because even if I attempted a fix, I won't see the results for another 5-10 hours. Is there anyway we can upgrade these two bots so that it won't be a burden for WebKit developers? Best, Ryosuke Niwa Software Engineer Google Inc. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Leopard Debug and Windows Debug test bots are too slow
I meant Leopard Debug (Tests) and Windows Debug (*WebKit2* Tests). - Ryosuke On Thu, Sep 9, 2010 at 11:17 PM, Ryosuke Niwa rn...@webkit.org wrote: Hi, It came to my attention that Leopard Debug (Tests) and Windows Debug (Test) are always behind by a significant amount (5-10 hours). Since Leopard and Windows are two major platforms we support, I would like to know when my patch broke these two platforms. However, because these two bots are 5-10 hours behind, it's really hard for me to realize any brokerage I caused or follow up later because even if I attempted a fix, I won't see the results for another 5-10 hours. Is there anyway we can upgrade these two bots so that it won't be a burden for WebKit developers? Best, Ryosuke Niwa Software Engineer Google Inc. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Leopard Debug and Windows Debug test bots are too slow
On Sep 10, 2010, at 2:20 AM, Ryosuke Niwa wrote: Windows Debug (WebKit2 Tests) I cleared out most of the old pending builds for this bot to try to help it catch up. It's interesting that ~45 minutes elapse between builds for the Windows WebKit2 bot, but only ~18 minutes elapse between builds for the SnowLeopard WebKit2 bot. We should figure out where the extra time is being spent! -Adam ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev