On Mar 10, 2011, at 3:40 PM, Adam Barth wrote:
On Thu, Mar 10, 2011 at 12:33 PM, Mark Rowe <[email protected]> wrote:
On 2011-03-10, at 12:27, Adam Barth wrote:
On Thu, Mar 10, 2011 at 12:11 PM, Mark Rowe <[email protected]> wrote:
On 2011-03-10, at 12:08, David Levin wrote:
tL;dr "Why isn't there a SnowLeopard debug buildbot? Related:
Why does the commit queue (appear) to only run release builds
through tests?"
Details:
Yesterday, I did a build of WebKit on SnowLeopard and hit ~12
crashes (mostly in inspector tests).
Then I realized that we don't have such a bot, so perhaps that's
why these crashes aren't getting noticed by people. It also
looks like the commit queue only runs release builds. I have a
concern that not having this allows the code to become less
stable than it should be.
The SnowLeopard Leaks bot builds and tests the debug configuration.
The problem with the leaks bot is that it's always red. At the
moment
it has 10792 leaks.
Fixing the leaks would help address this, and is obviously
beneficial in itself. It certainly didn't have anywhere near this
number of leaks last week.
What's the best way to tack down when that regression occurred? I
scrolled to the end of the waterfall for that builder
http://build.webkit.org/waterfall?last_time=1299183958&show=SnowLeopard%20Intel%20Leaks
and the earliest build I could find had 10344 leaks.
You can look at a page like:
http://build.webkit.org/builders/SnowLeopard%20Intel%20Leaks?numbuilds=500
And then you can start manually decreasing the build number on pages
like: http://build.webkit.org/builders/SnowLeopard%20Intel%20Leaks/builds/15273
-Adam
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
