[chromium-dev] Re: Stabilization Effort Daily Report
I reviewed all of the crashers that we have open. I was able to remove one and resolve a couple as duplicates or Won't Fix because they do not repro on the trunk. So... out of 26 we have resolved 12 (1 is upstream). All of the open issues have and owner. I appreciate everyone's help! Jon On Fri, Jan 23, 2009 at 12:40 PM, Jon j...@chromium.org wrote: *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=pMwul3Seofg448Q1VFJjsJAhl=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: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Stabilization Effort Daily Report
On Thu, Jan 15, 2009 at 11:08, Jon j...@chromium.org 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. 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=pMwul3Seofg448Q1VFJjsJAhl=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: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Stabilization Effort Daily Report
On Fri, Jan 9, 2009 at 11:32 AM, Jon j...@chromium.org wrote: Be sure to sign up at http://spreadsheets.google.com/ccc?key=pMwul3Seofg448Q1VFJjsJAhl=en if you are going to work on a layout test. We don't want to step on each other's toes. I just noticed Linux is on there. Has anyone else been working on Linux tests off of that sheet? I've just been fixing them directly and making my changes (and notes) on tests_fixable.txt. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Stabilization Effort Daily Report
On Thu, Jan 8, 2009 at 11:13 AM, Jon j...@chromium.org wrote: *Report for 2009-1-7* We need to make progress on the layout tests. Everyone should have their name next to at least one Layout Test. I still need owners for these two bugs, please take one of these: Issue 5541 http://code.google.com/p/chromium/issues/detail?id=5541: REGRESSION: bad drop-shadow rendering Issue 5559 http://code.google.com/p/chromium/issues/detail?id=5559: REGRESSION: cannot select text in gmail compose using shift+click if scroll between clicks *Layout Tests* No change since yesterday and the big jump was due to Ojan reclassifying a bunch of tests. We need to make progress. Layout tests are the bulk of the work and a day without progress is a big problem. To clarify, there was change yesterday. At least me, Finnur, and Rahul committed some layout test patches. The issue is that the daily webkit merge added 20 regressions (canvas), so the cumulative progress is negative. http://src.chromium.org/viewvc/chrome/trunk/src/webkit/tools/layout_tests/test_lists/tests_fixable.txt?r1=7684r2=7683pathrev=7684 Is anyone working on adding back the pixel array v8-binding? Be sure to sign up at http://spreadsheets.google.com/ccc?key=pMwul3Seofg448Q1VFJjsJAhl=en if you are going to work on a layout test. We don't want to step on each other's toes. [image: All+Tests=76.5][image: Want+To+Pass=92.5] http://spreadsheets.google.com/ccc?key=pMwul3Seofg4uTdanKb9iWw [image: History of passing tests %]http://spreadsheets.google.com/ccc?key=pMwul3Seofg4uTdanKb9iWw 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 23 of the 42 Purify issues. That is four more than yesterday. *Regressions* We have resolved 12 of 25 regressions. No progress yesterday. *Other bugs* We have also resolved 17 of the 42 other bugs. Only one more since yesterday. 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: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Stabilization Effort Daily Report
On Mon, Jan 5, 2009 at 10:49 PM, Jon j...@chromium.org wrote: 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/ I appreciate the enthusiasm! This isn't world-readable. Perhaps we should set up webspace on chromium.org for hosting these sorts of things? Dimitri's webkit merge tracker page would also be useful. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Stabilization Effort Daily Report
I am going to find a way to post Eric's stuff. It would be great to have a world visible web server that we can use to publish these internal reports. So far I have been using a script to update the SVN repository of the wiki on code.google.com which is not very satisfying. Jon On Tue, Jan 6, 2009 at 8:59 AM, Evan Martin e...@chromium.org wrote: On Mon, Jan 5, 2009 at 10:49 PM, Jon j...@chromium.org wrote: 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/ I appreciate the enthusiasm! This isn't world-readable. Perhaps we should set up webspace on chromium.org for hosting these sorts of things? Dimitri's webkit merge tracker page would also be useful. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
