Use command on Windows that ends quickly.

Use command on Windows that ends quickly.

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

[Bob Nystrom, 2012-10-30 19:33:31]

OK, trying this again. Just running "cmd.exe" doesn't exit, but this seems to
work better. The goal here is just to have an exe I can run that is found on the
PATH and exits quickly with a success return code.

[Emily Fortuna, 2012-10-30 19:42:53]

ah, makes sense. My previous guess was without looking at your tests too
closely, just from the descriptions. Sorry to have misled.

lgtm.

[ahe, 2012-10-31 06:43:35]

https://codereview.chromium.org/11339051/diff/2001/tests/standalone/io/proces...
File tests/standalone/io/process_path_environment_test.dart (right):

https://codereview.chromium.org/11339051/diff/2001/tests/standalone/io/proces...
tests/standalone/io/process_path_environment_test.dart:5: // Test that the
executable is looked up on the user's PATH when spawning a
I don't understand this test. Did it fail before CL 11260048 landed?

[Bob Nystrom, 2012-11-01 20:59:01]

On 2012/10/31 06:43:35, ahe wrote:
>
https://codereview.chromium.org/11339051/diff/2001/tests/standalone/io/proces...
> File tests/standalone/io/process_path_environment_test.dart (right):
> 
>
https://codereview.chromium.org/11339051/diff/2001/tests/standalone/io/proces...
> tests/standalone/io/process_path_environment_test.dart:5: // Test that the
> executable is looked up on the user's PATH when spawning a
> I don't understand this test. Did it fail before CL 11260048 landed?

Well, this test didn't exist before that patch. But, yes, if it had, it would
have been failing the entire time. That patch was specifically to fix that fact.