Re: jdk1.6 regresstion test failures: _Suite.junit and TestQueryObject with IllegalAccessException

[Lance J. Andersen]

Knut Anders Hatlen wrote: Sunitha Kambhampati <[EMAIL PROTECTED]> writes: I was looking at the test results from last weekend (09/01) on our test machines and I see the following failures on jdk1.6. derbyall/derbyall.fail:jdbc4/TestQueryObject.java derbyall/derbynetclientmats/derbynetclientmats.fail:jdbc4/TestQueryObject.java derbyall/derbynetclientmats/derbynetclientmats.fail:jdbc4/_Suite.junit Java Version: 1.6.0-rc,JRE - JDBC: Java SE 6 - JDBC 4.0 , jars are 10.3.0.0 alpha - (439522) The diffs looks like : ********* Diff file derbyall/jdbc40/TestQueryObject.diff *** Start: TestQueryObject jdk1.6.0-rc derbyall:jdbc40 2006-09-01 20:32:36 *** 0 add > java.sql.SQLException: Cannot insert new row into DataSet : Class com.sun.sql.DataSetImpl can not access a member of class org.apache.derbyTesting.functionTests.tests.jdbc4.TestData with modifiers "private" > Caused by: java.lang.IllegalAccessException: Class com.sun.sql.DataSetImpl can not access a member of class org.apache.derbyTesting.functionTests.tests.jdbc4.TestData with modifiers "private" > ... 14 more Test Failed. This was a bug in the jdk. Fixed in build 97 or 98, I think. build 98 is the lucky winner ********* Diff file derbyall/derbynetclientmats/DerbyNetClient/jdbc40/_Suite.diff *** Start: _Suite jdk1.6.0-rc DerbyNetClient derbynetclientmats:jdbc40 2006-09-01 21:27:16 *** 0 add > ............................F............. > There was 1 failure: > 1) testSetBinaryStreamLengthLessOnBlobTooLong(org.apache.derbyTesting.functionTests.tests.jdbc4.PreparedStatementTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:<22001> but was:<58009> > FAILURES!!! > Tests run: 2048, Failures: 1, Errors: 0 Test Failed. *** End: _Suite jdk1.6.0-rc DerbyNetClient derbynetclientmats:jdbc40 2006-09-01 21:27:39 *** ********* Diff file derbyall I believe Andreas checked in a fix for this. Let's see... Yes, DERBY-1800. Have these issues been fixed the last few days. If not, I can open jiras for these issues. Thank you for running these tests and reporting the results!