[Buildbot-devel] Purpose of buildbot.status.web.tests?

[Marc-Antoine Ruel]

On Tue, Nov 3, 2009 at 3:41 PM, Brian Warner <warner at lothar.com> wrote:
> This was intended to support the "Problem Tracking" feature that I
> always wanted but never got around to implementing. The idea would be to
> record fine-grained machine-parseable test results, instead of just a
> single full-suite SUCCESS/FAILURE and some unparseable logfiles. Then
> other tools could ask questions like "how frequently does
> buildbot.test.test_slaves.LatentSlave.testSequence fail?", or look for
> transitions from passing to failing and correlate them with the Changes
> that went into it.

We have the first part of what you ask. We call it the test flakiness dashboard.
http://build.chromium.org/buildbot/flakiness/

The upper section is one type of tests (webkit_tests, we call these
layout tests) and the lower section is a combination of all kinds of
unit tests being run (e.g. multiple steps on multiple builders). The
sources are near the rest of chromium buildbot sources if you want to
take a look.

There was no plan to upstream that since it's quite googletest and
webkit specific.

M-A

ref: http://code.google.com/p/googletest/