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=7684&r2=7683&pathrev=7684 Is anyone working on adding back the pixel array v8-binding? > 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. > [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 -~----------~----~----~----~------~----~------~--~---
