Marked tests as Timeout to match actual behavior.

Marked tests as Timeout to match actual behavior.

The tests service/{vm_timeline_events_test,coverage_test}.dart were
marked in service.status as possible timeouts, because I received
buildbot failure email that they had timed out.

The CL https://codereview.chromium.org/1779173003 that I had landed
only added 3 new test files and changed the status files for them, so
it is my interpretation that the timeouts are unrelated to my changes.

Committed: https://github.com/dart-lang/sdk/commit/2ee2fdb27c67b8cfb43c4960841097b985daf2ee

[eernst, 2016-03-11 18:29:39]

eernst@google.com changed reviewers:
+ johnmccutchan@google.com

[eernst, 2016-03-11 18:29:40]

TBR

[eernst, 2016-03-11 18:31:02]

Description was changed from

==========
Marked tests as Timeout to match actual behavior.

The tests service/{vm_timeline_events_test,coverage_test}.dart were
marked in service.status as possible timeouts, because I received
buildbot failure email that they had timed out.

The CL https://codereview.chromium.org/1779173003 that I had landed
only added 3 new test files and changed the status files for them, so
it is my interpretation that the timeouts are unrelated to my changes.
==========

to

==========
Marked tests as Timeout to match actual behavior.

The tests service/{vm_timeline_events_test,coverage_test}.dart were
marked in service.status as possible timeouts, because I received
buildbot failure email that they had timed out.

The CL https://codereview.chromium.org/1779173003 that I had landed
only added 3 new test files and changed the status files for them, so
it is my interpretation that the timeouts are unrelated to my changes.

Committed:
https://github.com/dart-lang/sdk/commit/2ee2fdb27c67b8cfb43c4960841097b985daf2ee
==========

[eernst, 2016-03-11 18:31:04]

Committed patchset #1 (id:1) manually as
2ee2fdb27c67b8cfb43c4960841097b985daf2ee (presubmit successful).

[Cutch, 2016-03-11 18:47:04]

On 2016/03/11 18:31:04, eernst wrote:
> Committed patchset #1 (id:1) manually as
> 2ee2fdb27c67b8cfb43c4960841097b985daf2ee (presubmit successful).

Hi,

Please revert this change as we don't hide these failures on the bots.

[eernst, 2016-03-11 19:10:49]

On 2016/03/11 18:47:04, Cutch wrote:
> On 2016/03/11 18:31:04, eernst wrote:
> > Committed patchset #1 (id:1) manually as
> > 2ee2fdb27c67b8cfb43c4960841097b985daf2ee (presubmit successful).
> 
> Hi,
> 
> Please revert this change as we don't hide these failures on the bots.

OK, I followed Florian L's advice on this, but it's reverted now.