Disable co19 on none-drt

Disable co19 on none-drt

Note that we currently don't run co19 on content_shell because co19 repsoitory
is not in dartium.deps/DEPS.

R=kasperl@google.com

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

[kasperl, 2013-10-04 09:35:03]

LGTM.

[kustermann, 2013-10-04 09:40:14]

Committed patchset #1 manually as r28256 (presubmit successful).

[ricow1, 2013-10-04 09:51:21]

LGTM

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

https://codereview.chromium.org/25958003/diff/1/tests/co19/co19-dartium.statu...
tests/co19/co19-dartium.status:6: *: Skip # running co19 tests on content_shell
would make our dartium cycle-times very long
I guess we can run them if we get incremental building going again

[kustermann, 2013-10-04 09:53:05]

On 2013/10/04 09:51:21, ricow1 wrote:
> LGTM
> 
> https://codereview.chromium.org/25958003/diff/1/tests/co19/co19-dartium.status
> File tests/co19/co19-dartium.status (right):
> 
>
https://codereview.chromium.org/25958003/diff/1/tests/co19/co19-dartium.statu...
> tests/co19/co19-dartium.status:6: *: Skip # running co19 tests on
content_shell
> would make our dartium cycle-times very long
> I guess we can run them if we get incremental building going again

It's not the building that takes the majority of the time. It's running
content_shell.
Remember we create a new content_shell process for every single test!

[ricow1, 2013-10-04 10:06:22]

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

https://codereview.chromium.org/25958003/diff/1/tests/co19/co19-dartium.statu...
tests/co19/co19-dartium.status:6: *: Skip # running co19 tests on content_shell
would make our dartium cycle-times very long
On 2013/10/04 09:51:21, ricow1 wrote:
> I guess we can run them if we get incremental building going again
I misread, this is just drt, so we are running it on dartium so we have full
coverage, thx