A comment on the big change in layout tests yesterday. We've added back the "defer" attribute for layout test expectations. Deferring means that we don't care about this test for the next release. So, when we have 0 non-deferred tests left to fix, the percentage of passing tests in this email will be 100%. Right now, the things that are deferred are all the tests we had deferred when we launched beta (~300 tests). For the most part, the only things we should defer are the tests that are for unimplemented features (e.g. video, workers, databases, etc). Ojan
On Wed, Jan 7, 2009 at 10:15 AM, Jon <j...@chromium.org> wrote: > *Report for 2009-1-6* > > I love seeing progress and we are making very good progress on both the > layout test front (+2.1%) and bugs (see chart below). I really appreciate > everyone pitching in. I suspect that our early successes with layout bugs > are due to some degree to us gathering in the low hanging fruit. We do have > a lot of tests which simply need a new baseline. Soon we will be past those > and onto the ugly ones! > > There are two bugs that need an owner, please take one of these: > > Issue 5541 <http://code.google.com/p/chromium/issues/detail?id=5541>: > REGRESSION: > bad drop-shadow rendering > > Issue 5559 <http://code.google.com/p/chromium/issues/detail?id=5559>: > REGRESSION: > cannot select text in gmail compose using shift+click if scroll between > clicks > > > *Layout Tests* > > Be sure to sign up at > http://spreadsheets.google.com/ccc?key=pMwul3Seofg448Q1VFJjsJA&hl=en if > you are going to work on a layout test. We don't want to step on each > other's toes. > [image: All+Tests=76.5][image: Want+To+Pass=92.5] > > <http://spreadsheets.google.com/ccc?key=pMwul3Seofg4uTdanKb9iWw> > > [image: History of passing tests > %]<http://spreadsheets.google.com/ccc?key=pMwul3Seofg4uTdanKb9iWw> > All Tests is based on all available layout tests including those that we > are currently not trying to pass. There are tests in this group which are > known to be bad or relate to future technologies. > > > Want to Pass is based on the tests that we need to be passing before we > will ship a revision of the browser. Getting this number as high as > possible is the goal of the stabilization effort. Some of these tests are > failing due to subtle changes that require the test to be re-baselined. > > > *Purify Bugs (Memory)* > > We have resolved 19 of the 41 Purify issues. That is NINE more than > Monday. > > > *Regressions* > > We have resolved 12 of 25 regressions. Nearly half-way! > > > *Other bugs* > > We have also resolved 16 of the 43 "other" bugs. Three since Monday! > > > So our bug burndown chart looks like this: > > As long as we keep the red line below the blue line we are on track for > the bugs. Keep in mind that this does not include the work on Layout Tests. > > You will find a lot more information about the Stabilization effort on the > Wiki at http://code.google.com/p/chromium/wiki/StabilizeTrunk > > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
