Marked tests as Timeout to match actual behavior.

Marked tests as Timeout to match actual behavior.

The test standalone/full_coverage_test.dart was marked in
standalone.status as a possible timeout, because I received buildbot
failure email that it 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/f741a16c63a35c0ed8a3757848f21e351d044366

[eernst, 2016-03-11 18:37:07]

Description was changed from

==========
Adjusted standalone.status to match actual timeouts.
==========

to

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

The test standalone/full_coverage_test.dart was marked in standalone.status as a
possible timeout, because I received buildbot failure email that it 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.
==========

[eernst, 2016-03-11 18:37:37]

Description was changed from

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

The test standalone/full_coverage_test.dart was marked in standalone.status as a
possible timeout, because I received buildbot failure email that it 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 test standalone/full_coverage_test.dart was marked in
standalone.status as a possible timeout, because I received buildbot
failure email that it 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.
==========

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

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

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

TBR

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

Description was changed from

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

The test standalone/full_coverage_test.dart was marked in
standalone.status as a possible timeout, because I received buildbot
failure email that it 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 test standalone/full_coverage_test.dart was marked in
standalone.status as a possible timeout, because I received buildbot
failure email that it 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/f741a16c63a35c0ed8a3757848f21e351d044366
==========

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

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