[chromium-dev] Stabilization Effort Daily Report

[Jon]

*Report for 2009-2-5*



*Layout Tests*

We have been making progress again and finally broke through that 300
barrier that was driving me crazy.  We are now over 96% which is great
progress!

 [image: All+Tests=78.2][image: Want+To+Pass=96.2]


[image: History of passing tests
%]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

This week I went back through the bug database looking for crashes on the
trunk.  Unfortunately, I found quite a few that should have been in stable.
 I was able to upstream one of them to WebKit and I have been trying to find
good dumps and stack traces.  Everyone who is assigned to a crasher should
be working on it.  As we saw at the Chrome Team meeting the trunk is
currently way behind the stable release.  Knocking off these key crashers is
very important.

http://code.google.com/p/chromium/issues/list?can=2&q=label:stable+label:crash+-Channel:stable


*Purify Bugs (Memory)*

We have 20 remaining Purify issues.


*Regressions*

We 11 remaining regressions.


*Other bugs*

We have 41 "other bugs" to resolve.


So our bug burndown chart looks like this:

  For now it would be great to concentrate on the crashers.  We don't want
to see attrition from our dev channel.  Also, 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] Stabilization Effort Daily Report

[Jon]

*Report for 2009-2-2*



*Layout Tests*

Our progress over the last few days has been flat.  We need to get below
that 300 bug line.

[image: All+Tests=78.0][image: Want+To+Pass=95.4]


[image: History of passing tests
%]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

We have 9 remaining crashers.


*Purify Bugs (Memory)*

We have 19 remaining Purify issues.


*Regressions*

We 7 remaining regressions, although that number is likely to go up.


*Other bugs*

We have 38 "other bugs" to resolve.


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] Stabilization Effort Daily Report

[Jon]

*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]



[image: History of passing tests
%]
  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: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---

[chromium-dev] Stabilization Effort Daily Report

[Jon]

*Report for 2009-1-20*

On Tuesday we we resolved 31 layout tests!  This is really great progress.
 At the same time we continue to be up with the tip of tree from WebKit so
the merges are landing regularly without causing us too much heartbreak.  At
this point, even at the rate of 9 a day, we could finish the first week of
March which would be amazing!



The Stability burndown chart got reset when a batch of un-reported Purify
bugs dropped in today.  To get those under control our bug squashing needs
to be at the rate of 6 a day for the next four weeks.  Many of these Purify
issues should be straightforward so I hope we can make up some ground
quickly.  I reset the blue line to reflect the required pace.

*Layout Tests*

We now pass more tests than we have ever passed.  With our All Tests
percentage nearing 80% we are doing better than ever before!
  [image: All+Tests=77.8][image: Want+To+Pass=95.4]



[image: History of passing tests
%]
 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 24 crashers we have assigned to "stable" we have resolved 7.  We have
been at the same place for a couple days.  We will need to make progress
here.  A recent editorial on
CNe t
mentions leaving Chrome for Firefox because dev channel releases are too
unreliable.


*Purify Bugs (Memory)*

We have resolved 28 of the 78 Purify issues.  That is eight more than last
Friday.


*Regressions*

We have resolved 17 of 28 regressions.


*Other bugs*

We have also resolved 21 of the 52 "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: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---

[chromium-dev] Stabilization Effort Daily Report

[Jon]

*Report for 2009-1-16*

We continue to make great progress on layout tests and we are ahead of pace
to finish by the end of the quarter.  Of course most of these early wins are
low-hanging fruit so we will eat into that lead as we move along but I have
to say that I love the look of this chart!


The Stability burndown chart got reset when a batch of un-reported Purify
bugs dropped in today.  To get those under control our bug squashing needs
to be at the rate of 6 a day for the next four weeks.  Many of these Purify
issues should be straightforward so I hope we can make up some ground
quickly.  I reset the blue line to reflect the required pace.

I still need an owner for this bug:

  Issue 5541 :
REGRESSION:
bad drop-shadow rendering


 *Layout Tests*

Since Monday we have resolved over 100 layout test failures!  That is more
than twice the pace we need to stay on target.  We also passed the 95% park
for tests we Want to Pass!  Fantastic!
  [image: All+Tests=77.5][image: Want+To+Pass=95.1]



[image: History of passing tests
%]
 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 24 crashers we have assigned to "stable" we have resolved 7.  That is
two more than yesterday.  We have been adding crashers to this list but I
have also been trying to weed out any that I can.


*Purify Bugs (Memory)*

We have resolved 20 of the 72 Purify issues.  There was a big batch of
Purify bugs that had not been entered into the bug tracker so if you look at
the chart you will see an explosion of issues.  Therefore I have reset the
blue line to take these into account.  There may be another 15 coming.


*Regressions*

We have resolved 18 of 28 regressions. We resolved one additional regression
since yesterday.


*Other bugs*

We have also resolved 21 of the 49 "other" bugs.


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] Stabilization Effort Daily Report

[Jon]

*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).

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 :
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]



[image: History of passing tests
%]
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 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] Stabilization Effort Daily Report

[Jon]

*Report for 2009-1-12*

We are on pace to fix the layout tests by the end of the quarter.  I really
appreciate everyone who is already contributing to this effort.  If you have
not yet experienced the distinct joy of fixing a layout test we happen to
have some more sitting around for you!  Anyone who is already listed on
http://go/layout-bugs will be happy to answer questions.

Yesterday I asked Tony and Eric to pose for the video camera.  We recorded
their Crash Course in Fixing Layout Tests.  Now I need to edit it.  Once I
am done we will post it to YouTube and encourage external engineers to try
their hand.  The more the merrier!


I still need an owner for this bug:

  Issue 5541 :
REGRESSION:
bad drop-shadow rendering


 *Layout Tests*

We had a net gain of 10 passing unit tests yesterday!  We need to fix at
least 9 so every additional fix is great!
 [image: All+Tests=76.3][image: Want+To+Pass=93.9]



[image: History of passing tests
%]
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.


*Purify Bugs (Memory)*

We have resolved 26 of the 42 Purify issues.  We resolved 3 additional
Purify bugs since the last email.


*Regressions*

We have resolved 15 of 25 regressions. We resolved two additional
regressions.


*Other bugs*

We have also resolved 20 of the 46 "other" bugs.  We resolved two more.


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] Stabilization Effort Daily Report

[Jon]

*Report for 2009-1-8*

As Eric pointed out, the progress we made was negated by new failures
introduced by the most recent WebKit merge.  This will likely continue to be
a problem.

If you have not yet resolved a layout test bug it would be good to take a
break from the other bugs and tackle one.  We are doing well on Purify and
the other bugs but need to gain some ground on layout tests.  A couple days
focusing on layout tests would be really helpful

I added a new chart to http://go/stable that shows the burndown for layout
tests.  It assumes we have until the end of the quarter.  The rate of fixes
needs to be about 9 a day if we are to hit our goal.  If you are not fixing
at least one a day then we are probably falling behind.  It is a lot of work
-- there just is no escaping the need to get these things fixed and the
longer it takes us the more likely we are to be even further behind by the
end of the quarter.


I still need owners for these two bugs, please take one of these:

  Issue 5541 :
REGRESSION:
bad drop-shadow rendering

 Issue 5559 :
REGRESSION:
cannot select text in gmail compose using shift+click if scroll between
clicks


 *Layout Tests*

We had a net gain of 2 passing unit tests yesterday.  We need to gain 9 each
day to be on pace to complete by the end of March.

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]



[image: History of passing tests
%]
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.  We did not resolve a new
Purify bug yesterday.


*Regressions*

We have resolved 13 of 25 regressions. We resolved one additional regression
yesterday.


*Other bugs*

We have also resolved 18 of the 42 "other" bugs.  We resolved 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] Stabilization Effort Daily Report

[Jon]

*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 :
REGRESSION:
bad drop-shadow rendering

 Issue 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.

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]



[image: History of passing tests
%]
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] Stabilization Effort Daily Report

[Jon]

*Report for 2009-1-6*

I love seeing progress and we are making very good progress on both the
layout test front (+2.1%) and bugs (see chart below).  I really appreciate
everyone pitching in.  I suspect that our early successes with layout bugs
are due to some degree to us gathering in the low hanging fruit.  We do have
a lot of tests which simply need a new baseline.  Soon we will be past those
and onto the ugly ones!

There are two bugs that need an owner, please take one of these:

Issue 5541 :REGRESSION:
bad drop-shadow rendering

Issue 5559 :REGRESSION:
cannot select text in gmail compose using shift+click if scroll between
clicks


*Layout Tests*

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]



[image: History of passing tests
%]
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 19 of the 41 Purify issues.  That is NINE more than Monday.


*Regressions*

We have resolved 12 of 25 regressions. Nearly half-way!


*Other bugs*

We have also resolved 16 of the 43 "other" bugs.  Three since Monday!


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] Stabilization Effort Daily Report

[Jon]

*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/
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
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  * 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
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: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---

[chromium-dev] Stabilization Effort Daily Report

[Jon]

*Report for 2009-12-23*

I have updated the Wiki so there is a 90 day trend report.  It will update
daily automatically.  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*

We have not made much improvement on the layout tests so far, although we
improved .2% on Want to Pass since yesterday.  The 90 day trend shows that
we have recovered from the webkit merges but we still have a long way to go.
 When everyone is back from the holidays we will be having a crash-course on
layout tests.  I hope to get this video-taped so we can share it broadly.

[image: To+Be+Fixed=0.6][image: All+Tests=74.9][image: Want+To+Pass=90.4]


The Fixed percentage is based on the layout tests in the
tests_fixable
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 8 of the 40 Purify issues.  No change since yesterday.


*Regressions*

We have resolved 10 of 25 regressions.  That is 2 more since yesterday.


*Other bugs*

We have also resolved 10 of the 41 "other" bugs.  That is 2 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] Stabilization Effort Daily Report

[Jon]

*Report for 2009-12-22*

Over the holiday this report won't be very daily but you get the picture.


*Layout Tests*

We have not made much improvement on the layout tests so far.  The 90 day
trend shows that we have recovered from the webkit merges but we still have
a long way to go.  When everyone is back from the holidays we will be having
a crash-course on layout tests.  I hope to get this video-taped so we can
share it broadly.
[image: To+Be+Fixed=1.4][image: All+Tests=74.8][image: Want+To+Pass=90.2]
[image: History of passing tests
%]

The Fixed percentage is based on the layout tests in the
tests_fixable
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.


This report is available at
http://www/~jonc/webkit.html for
Googlers.  I am trying to find a good way to make it available externally.
 Links to the same report for Mac and Linux is available as well from the
Wiki
.


*Purify Bugs (Memory)*

We have resolved 8 of the 40 Purify issues.  That is good progress.  Thank
you to everyone who is working on those
issues.



*Regressions*

We have resolved 8 of 25 regressions and upstreamed one of them to WebKit.
 This is also good progress.


*Other bugs*

We have also resolved  8 of the 41 "other" bugs.


So our bug burndown chart looks like this:

[image: pub.png]

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?ts=1229629370&updated=StabilizeTrunk

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Chromium-dev" group.
To post to this group, send email to chromium-dev@googlegroups.com
To unsubscribe from this group, send email to 
chromium-dev+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/chromium-dev?hl=en
-~--~~~~--~~--~--~---

<>