Closed plicease closed 8 years ago
Ah. I think this is partly a configuration issue. When the service goes down in the test, the windows firewall is dropping the packets, forcing timeouts, which is taking friggin' forever.
With a shorter timeout here are the errors that I am getting
Test Summary Report
-------------------
t\60_mark_down.t (Wstat: 0 Tests: 75 Failed: 0)
TODO passed: 60-68, 71-75
t\90_client.t (Wstat: 256 Tests: 7 Failed: 1)
Failed test: 3
Non-zero exit status: 1
t\91_client_4xhost.t (Wstat: 512 Tests: 2 Failed: 1)
Failed test: 2
Non-zero exit status: 2
Parse errors: Bad plan. You planned 6 tests but ran 2.
Files=27, Tests=1725, 124 wallclock secs ( 0.40 usr + 0.05 sys = 0.45 CPU)
Result: FAIL
and the test suite doesn't even pass after all that time.