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.
I meant Leopard Debug (Tests) and Windows Debug (*WebKit2* Tests). - Ryosuke On Thu, Sep 9, 2010 at 11:17 PM, Ryosuke Niwa <rniwa@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.
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
On Sep 10, 2010, at 8:11 AM, Adam Roben wrote:
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!
Looking at <http://build.webkit.org/builders/Windows%20Debug%20%28WebKit2%20Tests%29/builds/633> vs. <http://build.webkit.org/builders/SnowLeopard%20Intel%20Release%20%28WebKit2%20Tests%29/builds/1624>: jscore-test took 267 seconds on Windows vs. 18 seconds on SnowLeopard layout-test took 1711 seconds on Windows vs. 601 seconds on SnowLeopard That adds up to an extra 22.5 minutes on Windows, which explains most of the difference between the two. Perhaps the biggest issue is that Windows is using Debug builds, while Mac is using Release? Maybe we should change the Windows WebKit2 bot to use Release builds. -Adam
On Fri, Sep 10, 2010 at 5:15 AM, Adam Roben <aroben@apple.com> wrote:
On Sep 10, 2010, at 8:11 AM, Adam Roben wrote:
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!
Looking at < http://build.webkit.org/builders/Windows%20Debug%20%28WebKit2%20Tests%29/builds/633> vs. < http://build.webkit.org/builders/SnowLeopard%20Intel%20Release%20%28WebKit2%...
:
jscore-test took 267 seconds on Windows vs. 18 seconds on SnowLeopard layout-test took 1711 seconds on Windows vs. 601 seconds on SnowLeopard
That adds up to an extra 22.5 minutes on Windows, which explains most of the difference between the two.
Perhaps the biggest issue is that Windows is using Debug builds, while Mac is using Release? Maybe we should change the Windows WebKit2 bot to use Release builds.
I think changing to use release would make sense. -Sam
participants (3)
-
Adam Roben
-
Ryosuke Niwa
-
Sam Weinig