Army wrote:
I was trying to run some sanity checks as part of my work for DERBY-1758
and I noticed that the new JUnit test I created hangs when I run with
ibm131 and jdk131.
Actually, I gues that's not true. I don't see the hang with ibm131, only with
jdk131. Still seems like DERBY-300 could be the key, though...
And in any event, my original question stands: do we need to worry about this,
or should I just stop running JUnit tests on 1.3 JVMs?
My new test uses "TestConfiguration.defaultSuite()", which means the
test will run against embedded first and then against the Derby Client.
The embedded tests all complete without problem, but a hang occurs while
preparing for the client tests.
I think the underlying issue is DERBY-300, which is specific to 1.3
JVMs. And since we're saying that the 1.3 JVMs are deprecated as of
10.3, I guess the "solution" could just be to avoid running JUnit tests
on 1.3 JVMs.
Is that the correct conclusion, or is this something worth addressing,
presumably in the JUnit setup code somewhere?
Army
