*Report for 2009-1-5* The Layout Tests class went well. We are going to record it next week so people can watch it on demand. Eric's slides are at http://www.corp.google.com/~ericroman/layout/<http://www.corp.google.com/%7Eericroman/layout/> I appreciate the enthusiasm!
It is a good idea to look at http://code.google.com/p/chromium/wiki/StabilizeTrunk for the latest information. The Wiki also includes information on how to help fix layout tests. This is a great way to get involved and begin to learn the codebase. If you have ever wanted to be an open source developer then this is a great way to start! *Layout Tests* Each day the report at http://www.corp.google.com/~jonc/layout-summary.html<http://www.corp.google.com/%7Ejonc/layout-summary.html> will be updated with recent results. This report allows you to find layout tests that are failing on all platforms. It also makes it clear which directories have the most failures if you would like to work in a specific area. As always 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. Our hopes that the *jultomte <http://en.wikipedia.org/wiki/Tomte> * would fix all the layout tests did not pan out so we are going to have to do it ourselves. Here is where we currently stand: [image: To+Be+Fixed=1.4][image: All+Tests=74.9][image: Want+To+Pass=90.4] The Fixed percentage is based on the layout tests in the tests_fixable<http://src.chromium.org/viewvc/chrome/trunk/src/webkit/tools/layout_tests/test_lists/tests_fixable.txt?view=markup> file. These are tests we are currently ignoring because we know they fail. As soon as we fix them we move them out of fixable so this number does not tend to get very high. It can momentarily spike between the time we fix the test and update the file. 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 10 of the 40 Purify issues. That is two more than before the holiday break. *Regressions* We have resolved 11 of 25 regressions. That is one more since before the holiday break. *Other bugs* We have also resolved 12 of the 43 "other" bugs. That is 2 more than before the break but there are also 2 new ones. 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 -~----------~----~----~----~------~----~------~--~---
