Revert r13286 "Fix issues with test.dart that appeared on Mac."

Add back in "graceful shutdown code" for Windows, because the fix for
dartbug.com/1756 doesn't fix Windows.

Also revert my change in r13368 to find the source of this problem.
Committed: https://code.google.com/p/dart/source/detail?r=13379

[Emily Fortuna, 2012-10-08 21:14:05]

The addition of Mads's CL (http://code.google.com/p/dart/source/detail?r=13217)
is causing the Windows bots to hang. I suspect it is because the "graceful
shutdown" is not working as intended on Windows. I'll work on a better solution
that allows us to use the other CL, but for the meanwhile, I'm reverting so we
can get bot feedback.

[Emily Fortuna, 2012-10-08 21:16:14]

Some additional information: I logged in to the bot and made this change locally
on this bot, and you can see it starts behaving normally again:
http://chromegw.corp.google.com/i/client.dart/builders/dart2js-chrome-win7/bu...

[gram, 2012-10-08 22:02:43]

This looks okay to me, but I am concerned that this is going to fix the Windows
tests but break the Mac tests. Perhaps it would be better to revert to before
the HTTP server was added? AFAIK only Alan is using this, and based on
discussion with him it doesn't seem critical that he has this capability; it's a
nice to have but it could be mocked.

[Emily Fortuna, 2012-10-08 22:24:28]

PTAL -- I'm not making any changes except for the "graceful shutdown" code since
it doesn't work in Windows.

[gram, 2012-10-08 22:34:08]

https://codereview.chromium.org/11017022/diff/7001/tools/testing/dart/test_pr...
File tools/testing/dart/test_progress.dart (right):

https://codereview.chromium.org/11017022/diff/7001/tools/testing/dart/test_pr...
tools/testing/dart/test_progress.dart:89: if (_failedTests > 0) exit(1);
Did you intend to make this change? It seems the older version is more correct;
either way you want to call exit don't you?

https://codereview.chromium.org/11017022/diff/7001/tools/testing/dart/test_pr...
tools/testing/dart/test_progress.dart:241: if (_failedTests > 0) exit(1);
Ditto

[Emily Fortuna, 2012-10-08 22:37:23]

https://codereview.chromium.org/11017022/diff/7001/tools/testing/dart/test_pr...
File tools/testing/dart/test_progress.dart (right):

https://codereview.chromium.org/11017022/diff/7001/tools/testing/dart/test_pr...
tools/testing/dart/test_progress.dart:89: if (_failedTests > 0) exit(1);
On 2012/10/08 22:34:08, gram wrote:
> Did you intend to make this change? It seems the older version is more
correct;
> either way you want to call exit don't you?

Yes, this was intentional. As mentioned in the commit message -- this reverts
the change I made earlier this morning back to the way Mads had written it.

[gram, 2012-10-08 22:41:19]

lgtm

[Mads Ager (google), 2012-10-09 06:16:56]

https://codereview.chromium.org/11017022/diff/7001/tools/testing/dart/test_ru...
File tools/testing/dart/test_runner.dart (right):

https://codereview.chromium.org/11017022/diff/7001/tools/testing/dart/test_ru...
tools/testing/dart/test_runner.dart:765: new Timer(shutdownMillisecs, (e) { if
(!closed) _process.kill(); });
Please don't do this. If you add a 30 sec timeout the test script will hang for
30 seconds even when the processes die. Instead, if this is really needed on
Windows, set up a timer that you cancel when the process terminates.