*Report for 2009-1-28* Recent merges have taken a bit of a toll on our layout test passing rate. For the last few days we have been more or less flat on our progress. We are still on pace but we are losing that buffer that we will certainly need as we get into the harder bugs.
In the last few days we have made significant progress on the Issues with label:stable, as you can see by the graph at the bottom of this email. I really appreciate everyone who has contributed fixes recently. I have been trying very hard to review each of the open issues to throw out issues that do not apply and to ask for reductions or repro steps on everything. I hope when you pull up a bug to work on it that you have the information you need. If you don't -- email me. 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* Our progress over the last few days has been flat. We need to get below that 300 bug line. I am working on making the spreadsheet better. Hopefully I will get those changes in today. [image: All+Tests=78.1][image: Want+To+Pass=95.6] <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 26 crashers we have assigned to "stable" we have resolved 18! *Purify Bugs (Memory)* We have resolved 35 of the 77 Purify issues. *Regressions* We have resolved 21 of 26 regressions. The bad news here is that there appear to be some regressions that are missing the stable label and not showing up in the query. I will be looking for those over the next couple days. *Other bugs* We have also resolved 22 of the 53 "other" bugs. 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 -~----------~----~----~----~------~----~------~--~---
