> With a single check-in from Finnur we got a huge boost toward our goal of resolving all the layout test failures! I should point out that a big chunk of that was low-hanging fruit and that I don't deserve all of the credit. Evan Stade and I worked together on fixing some SVG issues and as a follow-up to that I was just going through the manual labor of re-baselining a bunch of layout tests that either had no/incorrect baseline and some that are now passing because of our work (and potentially work from others).
Oh... and lastly - maybe I should also mention that there is an even bigger chunk of layout test fixes coming soon (which also builds on some fixes from Brett). :) On Thu, Jan 15, 2009 at 12:21, Mark Larson (Google) <[email protected]>wrote: > > > On Thu, Jan 15, 2009 at 11:47, Mark Larson (Google) <[email protected]>wrote: > >> >> >> On Thu, Jan 15, 2009 at 11:08, Jon <[email protected]> wrote: >> >>> *Report for 2009-1-14* >>> >>> With a single check-in from Finnur we got a huge boost toward our goal of >>> resolving all the layout test failures! If you would like to try your hand >>> at fixing a layout test you can preview the 10 minute video we are preparing >>> at http://www/~jonc/layout1-2.m4v (assuming you don't all click at the >>> same time and can play MPEG4). >>> >>> >> Send internal links to internal mailing lists. It's frustrating to be told >> to check something out and then realize you're forbidden from accessing it. >> >> > > Oops. Didn't mean to spam chromium-dev with that. > > Just to clarify: Jon's going to publish the video on YouTube and post a > copy at dev.chromium.org when it's ready. The link he sent out is just a > preview of the work in progress. I didn't mean we shouldn't publish the > video, just that we shouldn't send out the internal-only link to the work in > progress to the whole world. > > I'll shut up now. > Mark > > >> >>> >>> This really is great progress and the sooner we get past these issues the >>> better! >>> >>> >>> I still need an owner for this bug: >>> >>> Issue 5541 <http://code.google.com/p/chromium/issues/detail?id=5541>: >>> REGRESSION: >>> bad drop-shadow rendering >>> >>> >>> *Layout Tests* >>> >>> We had a net gain of 34 passing unit tests yesterday! We are closing in >>> on 95% of Want to Pass! >>> [image: All+Tests=76.9][image: Want+To+Pass=94.5] >>> >>> <http://spreadsheets.google.com/ccc?key=pMwul3Seofg4uTdanKb9iWw> >>> >>> [image: History of passing tests >>> %]<http://spreadsheets.google.com/ccc?key=pMwul3Seofg4uTdanKb9iWw> >>> 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. >>> >>> 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. >>> >>> >>> >>> Crashers >>> >>> Of the 22 crashers we have assigned to "stable" we have resolved 5. As >>> we get more data from the dev channel we have been adding crashers to this >>> list. >>> >>> >>> *Purify Bugs (Memory)* >>> >>> We have resolved 29 of the 43 Purify issues. We resolved 6 additional >>> Purify bugs since the last email. >>> >>> >>> *Regressions* >>> >>> We have resolved 17 of 28 regressions. We resolved two additional >>> regressions. >>> >>> >>> *Other bugs* >>> >>> We have also resolved 21 of the 47 "other" bugs. We resolved one more. >>> >>> >>> So our bug burndown chart looks like this: >>> >>> We have popped above the blue line but we are making great progress >>> on layout tests. 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: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
