Update co19 to revision 6.

Update co19 to revision 6.

Committed: https://code.google.com/p/dart/source/detail?r=612

[ahe, 2011-10-21 18:26:34]

VM stats:
Total: 691 tests
 *   40 tests will be skipped
 *    0 tests are expected to be flaky but not crash
 *  586 tests are expected to pass
 *    0 tests are expected to fail that we won't fix
 *   60 tests are expected to fail that we should fix
 *    5 tests are expected to crash that we should fix
 *    0 tests are running in batch mode

dartc stats:
Total: 691 tests
 *    0 tests will be skipped
 *    0 tests are expected to be flaky but not crash
 *  548 tests are expected to pass
 *    0 tests are expected to fail that we won't fix
 *  143 tests are expected to fail that we should fix
 *    0 tests are expected to crash that we should fix
 *  691 tests are running in batch mode

Failure rates:

VM:  15%  ((40+60+5) * 100 / 691)
dartc: 21%  (143 * 100 / 691)

Notice, our friends in Russia have been busy today, and there are three new
revisions in the repository that came in after I started updating that status
files.

[Ivan Posva, 2011-10-21 18:41:58]

On 2011/10/21 18:26:34, ahe wrote:
> VM stats:
> Total: 691 tests
>  *   40 tests will be skipped
>  *    0 tests are expected to be flaky but not crash
>  *  586 tests are expected to pass
>  *    0 tests are expected to fail that we won't fix
>  *   60 tests are expected to fail that we should fix
>  *    5 tests are expected to crash that we should fix
>  *    0 tests are running in batch mode

These numbers do not add up to the status file being close to 300 lines. How is
that?

-Ivan

> 
> dartc stats:
> Total: 691 tests
>  *    0 tests will be skipped
>  *    0 tests are expected to be flaky but not crash
>  *  548 tests are expected to pass
>  *    0 tests are expected to fail that we won't fix
>  *  143 tests are expected to fail that we should fix
>  *    0 tests are expected to crash that we should fix
>  *  691 tests are running in batch mode
> 
> Failure rates:
> 
> VM:  15%  ((40+60+5) * 100 / 691)
> dartc: 21%  (143 * 100 / 691)
> 
> Notice, our friends in Russia have been busy today, and there are three new
> revisions in the repository that came in after I started updating that status
> files.

[ahe, 2011-10-21 18:43:58]

On 2011/10/21 18:41:58, Ivan Posva wrote:
> On 2011/10/21 18:26:34, ahe wrote:
> > VM stats:
> > Total: 691 tests
> >  *   40 tests will be skipped
> >  *    0 tests are expected to be flaky but not crash
> >  *  586 tests are expected to pass
> >  *    0 tests are expected to fail that we won't fix
> >  *   60 tests are expected to fail that we should fix
> >  *    5 tests are expected to crash that we should fix
> >  *    0 tests are running in batch mode
> 
> These numbers do not add up to the status file being close to 300 lines. How
is
> that?

My guess is that tests have been deleted. I'll try to come up with a way to
clean up the status files.

> 
> -Ivan
> 
> > 
> > dartc stats:
> > Total: 691 tests
> >  *    0 tests will be skipped
> >  *    0 tests are expected to be flaky but not crash
> >  *  548 tests are expected to pass
> >  *    0 tests are expected to fail that we won't fix
> >  *  143 tests are expected to fail that we should fix
> >  *    0 tests are expected to crash that we should fix
> >  *  691 tests are running in batch mode
> > 
> > Failure rates:
> > 
> > VM:  15%  ((40+60+5) * 100 / 691)
> > dartc: 21%  (143 * 100 / 691)
> > 
> > Notice, our friends in Russia have been busy today, and there are three new
> > revisions in the repository that came in after I started updating that
status
> > files.

[Ivan Posva, 2011-10-21 18:55:08]

On 2011/10/21 18:43:58, ahe wrote:
> On 2011/10/21 18:41:58, Ivan Posva wrote:
> > On 2011/10/21 18:26:34, ahe wrote:
> > > VM stats:
> > > Total: 691 tests
> > >  *   40 tests will be skipped
> > >  *    0 tests are expected to be flaky but not crash
> > >  *  586 tests are expected to pass
> > >  *    0 tests are expected to fail that we won't fix
> > >  *   60 tests are expected to fail that we should fix
> > >  *    5 tests are expected to crash that we should fix
> > >  *    0 tests are running in batch mode
> > 
> > These numbers do not add up to the status file being close to 300 lines. How
> is
> > that?
> 
> My guess is that tests have been deleted. I'll try to come up with a way to
> clean up the status files.

If it is just that then, LGTM.

We will have to clean them up anyway while fixing the issues. The real problem
is that the test names do not translate to file names so figuring out which
tests are still there is a non-trivial problem. Can we fix this problem?

-Ivan


> 
> > 
> > -Ivan
> > 
> > > 
> > > dartc stats:
> > > Total: 691 tests
> > >  *    0 tests will be skipped
> > >  *    0 tests are expected to be flaky but not crash
> > >  *  548 tests are expected to pass
> > >  *    0 tests are expected to fail that we won't fix
> > >  *  143 tests are expected to fail that we should fix
> > >  *    0 tests are expected to crash that we should fix
> > >  *  691 tests are running in batch mode
> > > 
> > > Failure rates:
> > > 
> > > VM:  15%  ((40+60+5) * 100 / 691)
> > > dartc: 21%  (143 * 100 / 691)
> > > 
> > > Notice, our friends in Russia have been busy today, and there are three
new
> > > revisions in the repository that came in after I started updating that
> status
> > > files.

[ahe, 2011-10-21 19:35:58]

Patch set number two removes the old cruft.

I'll submit the change now, walk home and look at the buildbot. I'll be walking
for about 30 minutes, so if the build bot goes red, please revert or update the
status file.

[Ivan Posva, 2011-10-21 22:48:14]

On 2011/10/21 19:35:58, ahe wrote:
> Patch set number two removes the old cruft.
> 
> I'll submit the change now, walk home and look at the buildbot. I'll be
walking
> for about 30 minutes, so if the build bot goes red, please revert or update
the
> status file.

Thanks!

-Ivan