#68 Error after leaving test runner over 24 hours

[jingkei]

I've been getting the following error on a test that I run indefinitely:

junit.framework.AssertionFailedError: Threads did not finish within -1 milliseconds

This always occurs after 86,403.859secs, which works out at just over 24 hours.

I've included the test case used to produce this error.

The full error output:
Time: 86,434.781
There was 1 failure:
1) testGrobo(TestGroboTimeout)junit.framework.AssertionFailedError: Threads did
not finish within -1 milliseconds.
at net.sourceforge.groboutils.junit.v1.MultiThreadedTestRunner.createTim
eoutError(MultiThreadedTestRunner.java:556)
at net.sourceforge.groboutils.junit.v1.MultiThreadedTestRunner.setTimeou
tError(MultiThreadedTestRunner.java:528)
at net.sourceforge.groboutils.junit.v1.MultiThreadedTestRunner.runTestRu
nnables(MultiThreadedTestRunner.java:224)
at net.sourceforge.groboutils.junit.v1.MultiThreadedTestRunner.runTestRu
nnables(MultiThreadedTestRunner.java:150)
at TestGroboTimeout.testGrobo(TestGroboTimeout.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at TestGroboTimeout.main(TestGroboTimeout.java:16)

[jingkei]

A JUnit test case to reproduce timeout problem