*Report for 2009-1-22* While our layout test progress looks great I am increasingly worried about crashers. We held back the 2.0.158.0 dev release because it is crashing too much. Having regular dev channel releases is very important to me because I think it helps us find problems early. I will try to get the crashers list fixed up so they represent the big offenders so we can make the most progress with the least effort.
If you are frustrated with http://crash you may want to try Dremel with Crash. Anthony sent out an email about this a little while ago. It provides you with a SQL-ish interface to Crash. If you have a useful query I would appreciate it if you would share it with the class. :) *Layout Tests* We are closing on average 10 layout tests a day. We need a pace of at least 9 a day to stay on target for the end of the quarter so we are gaining ground. It is likely that the pace will get harder to maintain as we go along so it is great that we have gained some headroom! [image: All+Tests=78.2][image: Want+To+Pass=95.7] <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 27 crashers we have assigned to "stable" we have resolved 8. *Purify Bugs (Memory)* We have resolved 28 of the 78 Purify issues. That is the same as Wednesday. *Regressions* We have resolved 17 of 28 regressions. That is the same as Wednesday. *Other bugs* We have also resolved 21 of the 53 "other" bugs. That is the same as Wednesday. So our bug burndown chart looks like this: I reset the blue line after a bunch of Purify bugs from UI tests landed all at once. 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 -~----------~----~----~----~------~----~------~--~---
