Thilo Goetz wrote:
It's our old friend the type priorities again. Even though the test
case does not use type priorities, types are sorted differently in
the type system depending on JVM version. So the test case went
through with JDK 1.6_1, but not 1.5_7, for example. This sucks.
Since I don't have time to go after the root cause of this, I have
modified the test case to remove this dependency.
As I recall, the type order changes when there is no ordering specified,
because it depends on
the order returned from "hashing"; and the hash function changed from
jdk to jdk.
-Marshall
--Thilo
Thilo Goetz wrote:
Marshall Schor wrote:
Running org.apache.uima.cas.test.AnnotationTreeTest
testTree(org.apache.uima.cas.test.AnnotationTreeTest) Time elapsed:
0.16 sec <<< FAILURE!
junit.framework.AssertionFailedError
at
junit.framework.AssertionFailedError.<init>(AssertionFailedError.java:11)
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertTrue(Assert.java:27)
at
org.apache.uima.cas.test.AnnotationTreeTest.testTree(AnnotationTreeTest.java:85)
Does anyone else have this failure? -Marshall
I see it too, but only when running all tests with mvn install. Running
the test individually works fine. I'll investigate.
--Thilo
