Pub integration tests sometimes need more than 20 seconds.

Pub integration tests sometimes need more than 20 seconds.

Also, revert "Increase timeout of some pub tests."

This reverts commit r26976.

BUG=http://dartbug.com/12983
R=kustermann@google.com

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

[kustermann, 2013-09-03 07:32:38]

https://codereview.chromium.org/23444032/diff/1/dart/sdk/lib/_internal/pub/te...
File dart/sdk/lib/_internal/pub/test/test_pub.dart (right):

https://codereview.chromium.org/23444032/diff/1/dart/sdk/lib/_internal/pub/te...
dart/sdk/lib/_internal/pub/test/test_pub.dart:42: unittestConfiguration.timeout
= const Duration(seconds: 60);
That's not the best thing to do. If this test is really timing out, the result
of the test can sometimes be 'FAIL' (if this timer fires first) or 'TIMEOUT' (if
the timer of test.dart fires first).
(i.e. due to the fact that test.dart is also using a 60 second timeout).

There are two alternatives:
- making an opt-out solutions and using it here
- lowering the timeout to 30-45 seconds

A hackisch way of 'opt-out' would be:
  unittestConfiguration.timeout = const Duration(hours: 24)

[ahe, 2013-09-03 08:13:07]

PTAL

[kustermann, 2013-09-03 08:31:02]

LGTM

[ahe, 2013-09-03 08:33:18]

Committed patchset #2 manually as r27031 (presubmit successful).

[Bob Nystrom, 2013-09-03 15:21:03]

LGTM.

[kustermann, 2013-09-03 15:26:42]

On 2013/09/03 15:21:03, Bob Nystrom wrote:
> LGTM.

dartdoc/test/dartdoc_test is also hitting the limit in checked mode. See:
http://build.chromium.org/p/client.dart/builders/pub-linux/builds/11323/steps...