Looks like a good start. Have you considered a test-centric view (instead of a bot-centric view)? That might make it easier to see what's going on globally across the project. Adam On Wed, Jun 1, 2011 at 12:22 PM, Adam Roben <aroben@apple.com> wrote:

Hi all-

Before I go on vacation for 2.5 weeks, I wanted to let you know about a new page I've been working on on build.webkit.org. You can see it here:

http://build.webkit.org/TestFailures/

The idea of the page is to provide a single place to go to find out what tests are failing on the bots and when they started failing. It also tries to make it easy to file bugs about the failures.

It is pretty ugly, and has some glaring bugs (search Bugzilla for "TestFailures"). But I've found it useful already. I hope you will, too!

Please file bugs and feature requests in the Tools / Tests component of Bugzilla, include the word "TestFailures" in the bug, and CC me. The code lives in Tools/BuildSlaveSupport/build.webkit.org-config/public_html/TestFailures.

Let me know what you think!

-Adam

_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

I've been working a bit more on TestFailures over the last few weeks, and it's grown a few new features [1]. I encourage you to check it out if you haven't, and even if you have! http://build.webkit.org/TestFailures/ -Adam 1. Including: * Basic support for detecting flaky tests * Basic support for NRWT bots * LocalStorage caching for speeeeed! * Lists of existing bugs related to the failing tests * Parsing of commit messages to try to guess better which revision is guilty * Loading of builds that have been moved to the old-results directory * Crashing function names shown right on the page * Links to regression ranges in Trac * A link right on the page to file a bug about TestFailures itself