refactor timing tests to not use the test framework

refactor timing tests to not use the test framework

BUG=
R=brianwilkerson@google.com

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

[keertip, 2015-10-19 21:49:43]

keertip@google.com changed reviewers:
+ brianwilkerson@google.com

[Brian Wilkerson, 2015-10-19 22:50:32]

LGTM

https://codereview.chromium.org/1419503002/diff/20001/pkg/analysis_server/ben...
File pkg/analysis_server/benchmark/perf/analysis_timing_tests.dart (right):

https://codereview.chromium.org/1419503002/diff/20001/pkg/analysis_server/ben...
pkg/analysis_server/benchmark/perf/analysis_timing_tests.dart:78:
stopwatch.reset();
Does 'reset' also stop the clock? If not, we should probably just stop it. I'm
not sure what the value of resetting it is in any case. (And I'd actually stop
it before the call to 'print', but I'm not sure there's a good reason for doing
so.)

[keertip, 2015-10-19 23:10:11]

https://codereview.chromium.org/1419503002/diff/20001/pkg/analysis_server/ben...
File pkg/analysis_server/benchmark/perf/analysis_timing_tests.dart (right):

https://codereview.chromium.org/1419503002/diff/20001/pkg/analysis_server/ben...
pkg/analysis_server/benchmark/perf/analysis_timing_tests.dart:78:
stopwatch.reset();
On 2015/10/19 22:50:32, Brian Wilkerson wrote:
> Does 'reset' also stop the clock? If not, we should probably just stop it. I'm
> not sure what the value of resetting it is in any case. (And I'd actually stop
> it before the call to 'print', but I'm not sure there's a good reason for
doing
> so.)

Will remove it. This is cruft from when we were trying to run the test multiple
times, and it made sense to reset the stopwatch.

[keertip, 2015-10-19 23:35:14]

Committed patchset #3 (id:40001) manually as
2a88bdac4adcc50a40d8f0724827b4bbfe949695 (presubmit successful).