[webkit-dev] new-run-webkit-tests new results.html format
eric at webkit.org
Tue May 3 14:23:36 PDT 2011
IIRC the "showing wdiff when there is no wdiff" bug has since been
fixed? (but that bot just hasn't updated?)
what's the "failure type" column? (and why can't I select its text?)
Why do expected flaky tests show up in the "Expected to fail but passed" list?
Seems expected flaky tests should be in some sort of separate
(less-obvious, possibly hidden-by-default) table. It looks like
they're currently split between the failure and the pass tables when
wether they passed or failed doesn't seem relevant to this run.
On Tue, May 3, 2011 at 2:18 PM, Dirk Pranke <dpranke at chromium.org> wrote:
> Here is a link to the NRWT bot running the Mac Leopard Release build:
> -- Dirk
> On Tue, May 3, 2011 at 2:14 PM, Eric Seidel <eric at webkit.org> wrote:
>> Is that a good example? It doesn't remind me much of the ORWT output.
>> The disclosure triangles don't seem to do anything for hte failures on
>> that page.
>> On Tue, May 3, 2011 at 2:05 PM, Ojan Vafai <ojan at chromium.org> wrote:
>>> On Tue, May 3, 2011 at 1:44 PM, Adam Roben <aroben at apple.com> wrote:
>>>> On May 3, 2011, at 4:01 PM, Ojan Vafai wrote:
>>>> The results load considerably faster now. For runs where many tests fail,
>>>> the filesize is considerably smaller than the
>>>> old-run-webkit-tests filesize. Also, I've added in the image toggling
>>>> behavior of old-run-webkit-tests and made the aesthetics a bit closer to the
>>>> old-run-webkit-test format.
>>>> Some rough file sizes if you care about the details.
>>>> old-run-webkit-tests 5 failures: 5k
>>>> old-run-webkit-tests 500 failures: 250k
>>>> new-run-webkit-tests 5 failures: 1k json + 25k htmljs
>>>> new-run-webkit-tests 500 failures: 60k json + 25k html/js
>>>> Thanks for all the work you've put into this, Ojan! Is there a link we can
>>>> use to look at the latest and greatest?
>>> Disclaimer: The json file loaded on that page is much larger (~90x) than the
>>> non-Chromium equivalent would be because Chromium runs tests expected to
>>> webkit-dev mailing list
>>> webkit-dev at lists.webkit.org
More information about the webkit-dev