Update co19 test suite to r706

Update co19 test suite to r706

BUG=dartbug.com/17758
R=kustermann@google.com

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

[Bill Hesse, 2014-03-25 15:59:01]

I'm running the ie9 tests now, but they are very slow.

[kustermann, 2014-03-25 16:30:40]

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-analyzer.status
File tests/co19/co19-analyzer.status (right):

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-analyzer.sta...
tests/co19/co19-analyzer.status:53: # co19 issue 639 is closed as fixed, so any
remaining failures should be triaged:
Remove that comment.

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-analyzer.sta...
tests/co19/co19-analyzer.status:58: LibTest/isolate/IsolateStream/first_A02_t01:
Fail # Please triage this issue.
I would use the usual naming convention, so someone can easily identify which
co19 roll caused it:

# co19-roll r706: Please triage this failure

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-analyzer.sta...
tests/co19/co19-analyzer.status:141:
Language/12_Expressions/15_Method_Invocation/4_Super_Invocation_A06_t03:
StaticWarning # Issue 17758. Please triage this failure.
The dartbug tells to look into co19-dartium.status, not into this file. Why do
you mark these with that issue number?

If they are common between dartium and analyzer, should they belong into
co19-co19.status?

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-analyzer2.st...
File tests/co19/co19-analyzer2.status (right):

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-analyzer2.st...
tests/co19/co19-analyzer2.status:53: # co19 issue 639 is closed as fixed, so any
remaining failures should be triaged:
Same comments as in other file.

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dart2js.status
File tests/co19/co19-dart2js.status (right):

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dart2js.stat...
tests/co19/co19-dart2js.status:131: LibTest/core/Map/Map_class_A01_t04: Skip #
Times out even with Slow tag.
There is no issue number, no timeout marker, no "pleas triage this failure".
Why?

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dart2js.stat...
tests/co19/co19-dart2js.status:579: # Could this be dart issue 7728?  Yes, it
is!
Remove this comment.

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dart2js.stat...
tests/co19/co19-dart2js.status:597: LibTest/async/Timer/isActive_A01_t02:
RuntimeError # Issue 7728
To make it easy to see, you could add "# Issue 7728, timer not supported in
d8/jsshell'

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dartium.status
File tests/co19/co19-dartium.status (right):

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dartium.stat...
tests/co19/co19-dartium.status:28: LibTest/isolate/RawReceivePort/close_A01_t01:
RuntimeError # Issue 14626
This issue was marked as Area-Test. How owns that? Who will fix it?

[Bill Hesse, 2014-03-25 17:18:10]

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-analyzer.status
File tests/co19/co19-analyzer.status (right):

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-analyzer.sta...
tests/co19/co19-analyzer.status:141:
Language/12_Expressions/15_Method_Invocation/4_Super_Invocation_A06_t03:
StaticWarning # Issue 17758. Please triage this failure.
On 2014/03/25 16:30:41, kustermann wrote:
> The dartbug tells to look into co19-dartium.status, not into this file. Why do
> you mark these with that issue number?
> 
> If they are common between dartium and analyzer, should they belong into
> co19-co19.status?

This is a mistake.  These should be labeled with a different meta-issue for
untriaged co19 analyzer failures.

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dartium.status
File tests/co19/co19-dartium.status (right):

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dartium.stat...
tests/co19/co19-dartium.status:28: LibTest/isolate/RawReceivePort/close_A01_t01:
RuntimeError # Issue 14626
On 2014/03/25 16:30:41, kustermann wrote:
> This issue was marked as Area-Test. How owns that? Who will fix it?

It also includes a reference to issue 13921, which is basically a duplicate of
it, with more detail.  This is marked as area library, and has a number of
people CCd on it.

This problem is an interaction of dart:isolate, dart:html (DOM), and testing. 
It is unclear how we will solve it.  I think these should be marked 13921, and
14626 should be marked a duplicate of 13921.

[kustermann, 2014-03-25 17:35:36]

rubberstamp lgtm :)

[Bill Hesse, 2014-03-27 11:55:18]

Update co19 test suite to r706

[Bill Hesse, 2014-03-27 12:13:45]

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-analyzer.status
File tests/co19/co19-analyzer.status (right):

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-analyzer.sta...
tests/co19/co19-analyzer.status:53: # co19 issue 639 is closed as fixed, so any
remaining failures should be triaged:
On 2014/03/25 16:30:41, kustermann wrote:
> Remove that comment.

Done.

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-analyzer.sta...
tests/co19/co19-analyzer.status:58: LibTest/isolate/IsolateStream/first_A02_t01:
Fail # Please triage this issue.
On 2014/03/25 16:30:41, kustermann wrote:
> I would use the usual naming convention, so someone can easily identify which
> co19 roll caused it:
> 
> # co19-roll r706: Please triage this failure

Done.

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-analyzer2.st...
File tests/co19/co19-analyzer2.status (right):

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-analyzer2.st...
tests/co19/co19-analyzer2.status:53: # co19 issue 639 is closed as fixed, so any
remaining failures should be triaged:
On 2014/03/25 16:30:41, kustermann wrote:
> Same comments as in other file.

Done.

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dart2js.status
File tests/co19/co19-dart2js.status (right):

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dart2js.stat...
tests/co19/co19-dart2js.status:131: LibTest/core/Map/Map_class_A01_t04: Skip #
Times out even with Slow tag.
On 2014/03/25 16:30:41, kustermann wrote:
> There is no issue number, no timeout marker, no "pleas triage this failure".
> Why?

Done.

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dart2js.stat...
tests/co19/co19-dart2js.status:579: # Could this be dart issue 7728?  Yes, it
is!
On 2014/03/25 16:30:41, kustermann wrote:
> Remove this comment.

Done.

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dart2js.stat...
tests/co19/co19-dart2js.status:597: LibTest/async/Timer/isActive_A01_t02:
RuntimeError # Issue 7728
On 2014/03/25 16:30:41, kustermann wrote:
> To make it easy to see, you could add "# Issue 7728, timer not supported in
> d8/jsshell'

Done.

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dartium.status
File tests/co19/co19-dartium.status (right):

https://codereview.chromium.org/211383002/diff/1/tests/co19/co19-dartium.stat...
tests/co19/co19-dartium.status:28: LibTest/isolate/RawReceivePort/close_A01_t01:
RuntimeError # Issue 14626
On 2014/03/25 17:18:10, Bill Hesse wrote:
> On 2014/03/25 16:30:41, kustermann wrote:
> > This issue was marked as Area-Test. How owns that? Who will fix it?
> 
> It also includes a reference to issue 13921, which is basically a duplicate of
> it, with more detail.  This is marked as area library, and has a number of
> people CCd on it.
> 
> This problem is an interaction of dart:isolate, dart:html (DOM), and testing. 
> It is unclear how we will solve it.  I think these should be marked 13921, and
> 14626 should be marked a duplicate of 13921.

Done.

[Bill Hesse, 2014-03-27 12:14:19]

Committed patchset #4 manually as r34468 (presubmit successful).