I finally wrote a mini-design doc for the layout test
dashboardhttp://www.chromium.org/developers/design-documents/layout-tests-results-dashboard
.
Getting this to work for other tests (e.g. browser_tests, unit_tests, etc)
would be a pretty small amount of Python work. If anyone is interested in
A few changes to the layout test dashboard you might not be aware of if you
haven't used it in a while:
- You can see the expected results, actual results and diffs between the
two for a given test. This is especially useful when doing rebaseline code
reviews. The results shown are the
For those of you who rely on the layout test dashboard for identifying
flakiness, my apologies. I accidentally checked in some test code (one
number was wrong!) and clobbered all but 10 of the runs of data for each
builder. There's no way to recover it. We'll just need to wait for enough
runs for
A first version of the layout test flakiness dashboard is up.
http://src.chromium.org/viewvc/chrome/trunk/src/webkit/tools/layout_tests/flakiness_dashboard.html
Some of the key features:
- updates roughly as quickly as the bots have run the tests (no
post-processing, stdio parsing or
