On Tue, Sep 22, 2009 at 10:26 AM, Jeffrey Chang <jeffr...@google.com> wrote:
>
>
> - Fix all Windows layout tests: make test_expectations.txt only contain
> items that we will never fix, features we have not yet implemented, or bugs
> less than one week old that are a result of a recent WebKit merge.
> - Set up a public dashboard which tracks the number of failing layout
> tests over time on the Chromium site.
>
>
How do you intend to track these numbers? Right now we have no way to
distinguish between failures that need fixing versus failures due to
unimplemented features. One way would be to use DEFER again. All the support
is still there, and the initial code for the tracking dashboard exposes it.
It would mostly just work.
I propose that we bring back to defer, but use it *only* for tests that fail
due to unimplemented features.
Ojan
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
