Yes, exactly. I'm working on some additional reports and dashboards that will allow us to track the funnel of finds/fixes better as well.
-- Dirk On Tue, Sep 22, 2009 at 11:38 AM, Dimitri Glazkov <[email protected]> wrote: > > Yep. Dirk was the one to suggest bringing it back. I didn't put this > in the documentation, but only because I wasn't yet sure whether we'll > track them by bug milestone or explicitly using the tag. > > :DG< > > On Tue, Sep 22, 2009 at 11:33 AM, Ojan Vafai <[email protected]> wrote: >> On Tue, Sep 22, 2009 at 10:26 AM, Jeffrey Chang <[email protected]> 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: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
