Windows test suite timeouts

[Matt Mackall]

On Thu, 2013-01-03 at 22:06 -0500, Matt Harbison wrote:
> Every so often, I've noticed that some tests on Windows will take a 
> really long time, and then timeout:
> 
>    $ python run-tests.py -i test-largefiles.t
> 
>    ERROR: c:\Users\Matt\Projects\hg\tests\test-largefiles.t timed out
>    t
>    Failed test-largefiles.t: timed out
>    # Ran 1 tests, 0 skipped, 1 failed.
> 
> It seems like once this occurs, it will occur every time until a reboot.

Neat! This probably puts you pretty close to finding the problem we see
on the buildbot.

> Is there something I can do to debug this?  Is this a known issue?  If 
> so, is there a process that needs to be killed or a file deleted so the 
> tests can be run again without rebooting?

Unfortunately, tests are no longer just shell scripts that you can run
outside the harness. But you can do:

$ ./run-tests.py -d test-largefiles.t

..and then it runs on the console (with high salinity). Interestingly
enough, it stops with a prompt here.

-- 
Mathematics is the supreme nostalgia of our time.