On Tue, Oct 19, 2010 at 11:44 AM, Alexey Proskuryakov <[email protected]> wrote:
> I agree that raising awareness of which tests or code areas are flaky seems > useful. One problem I personally had was with digging up data on flakiness. > The link for a dashboard that I found was < > http://test-results.appspot.com/dashboards/flakiness_dashboard.html> - the > URL was freezing my browser for several minutes on each move, and I couldn't > make sense of what it was telling me UI-wise quickly enough. I'm not even > sure how it's related to flakiness seen by commit queue, as it seems to be > about chromium. That dashboard currently only supports the Chromium bots. If other bots successfully switch over to new-run-webkit-tests, we'll be able to easily add them to that dashboard. The freezing issue is a recent one I plan on looking into soon. WebKit is ridiculously slow at rendering this HTML for some reason (it's a single large table). The UI is very dense and confusing, but it gives you quite a bit of useful information. Here's some limited documentation on making sense of the dashboard UI: http://sites.google.com/a/chromium.org/dev/developers/testing/flakiness-dashboard Ojan
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
