*Report for 2009-1-12* We are on pace to fix the layout tests by the end of the quarter. I really appreciate everyone who is already contributing to this effort. If you have not yet experienced the distinct joy of fixing a layout test we happen to have some more sitting around for you! Anyone who is already listed on http://go/layout-bugs will be happy to answer questions.
Yesterday I asked Tony and Eric to pose for the video camera. We recorded their Crash Course in Fixing Layout Tests. Now I need to edit it. Once I am done we will post it to YouTube and encourage external engineers to try their hand. The more the merrier! 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 10 passing unit tests yesterday! We need to fix at least 9 so every additional fix is great! [image: All+Tests=76.3][image: Want+To+Pass=93.9] <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. *Purify Bugs (Memory)* We have resolved 26 of the 42 Purify issues. We resolved 3 additional Purify bugs since the last email. *Regressions* We have resolved 15 of 25 regressions. We resolved two additional regressions. *Other bugs* We have also resolved 20 of the 46 "other" bugs. We resolved two more. 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: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
