On 1/14/16 11:00 PM, Ingemar Aberg wrote:
On 2016-01-12 11:43, Ingemar Aberg wrote:
Hi,
I decided to take a look at the status of the Java DB tests and after
fixing the JDK9 Tendril resource I saw that the new JDK9 version
string format (Verona, JEP: http://openjdk.java.net/jeps/223) breaks
the derbyTesting harness:
Exception in thread "main"
java.lang.StringIndexOutOfBoundsException: begin 0, end -1, length 4
at java.lang.String.checkBoundsBeginEnd(String.java:3122)
at java.lang.String.substring(String.java:1910)
at
org.apache.derbyTesting.functionTests.harness.JavaVersionHolder.<init>(JavaVersionHolder.java:44)
at
org.apache.derbyTesting.functionTests.harness.RunSuite.getSuiteProperties(RunSuite.java:304)
at
org.apache.derbyTesting.functionTests.harness.RunSuite.main(RunSuite.java:122)
Anyone interested in trying to fix this?
/ingo
A couple of tests in suites.All also fail on all platforms with
suspiciously similar error messages:
org.apache.derbyTesting.functionTests.tests.lang.MathTrigFunctionsTest.testRadians
java.lang.StringIndexOutOfBoundsException: begin 0, end -1, length 4
at java.lang.String.checkBoundsBeginEnd(String.java:3122)
at java.lang.String.substring(String.java:1910)
at
org.apache.derbyTesting.functionTests.harness.JavaVersionHolder.<init>(JavaVersionHolder.java:44)
at
org.apache.derbyTesting.junit.BaseTestCase.vmAtLeast(BaseTestCase.java:1235)
at
org.apache.derbyTesting.functionTests.tests.lang.MathTrigFunctionsTest.testRadians(MathTrigFunctionsTest.java:686)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:120)
at
org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:443)
at
org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:460)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:58)
org.apache.derbyTesting.functionTests.tests.jdbc4.UnsupportedVetter.testSupportedMethods
junit.framework.AssertionFailedError: unsupportedList expected:<0>
but was:<8>
at
org.apache.derbyTesting.functionTests.tests.jdbc4.UnsupportedVetter.testSupportedMethods(UnsupportedVetter.java:381)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:120)
at
org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:443)
at
org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:460)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:58)
/ingo
Moving this discussion to the developer list:
Hi Ingo,
I have checked in a patch (derby-6854-01-aa-fixFor9-ea.diff, revision
1725139), which hopefully allows tests to run cleanly against a Derby
which is built by Java 8 and tested on Java 9.
Along the way, I discovered that we can no longer build Derby with early
access releases of Java 9. I have opened 2 issues for addressing these
problems: https://issues.apache.org/jira/browse/DERBY-6855 and
https://issues.apache.org/jira/browse/DERBY-6856.
Please let us know if you see further problems.
Thanks,
-Rick