You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Sunitha Kambhampati <ks...@gmail.com> on 2006/09/07 23:11:47 UTC
jdk1.6 regresstion test failures: _Suite.junit and TestQueryObject
with IllegalAccessException
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.
********* 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
Have these issues been fixed the last few days. If not, I can open
jiras for these issues.
Thanks,
Sunitha.
Re: jdk1.6 regresstion test failures: _Suite.junit and TestQueryObject
with IllegalAccessException
Posted by Andreas Korneliussen <An...@Sun.COM>.
..
> ********* 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
>
> Have these issues been fixed the last few days. If not, I can open
> jiras for these issues.
The last issue has been fixed on trunk (DERBY-1800)
Regards
Andreas
> Thanks,
> Sunitha.
>
>
Re: jdk1.6 regresstion test failures: _Suite.junit and TestQueryObject
with IllegalAccessException
Posted by "Lance J. Andersen" <La...@Sun.COM>.
Knut Anders Hatlen wrote:
> Sunitha Kambhampati <ks...@gmail.com> 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!
>
>
Re: jdk1.6 regresstion test failures: _Suite.junit and TestQueryObject
with IllegalAccessException
Posted by Sunitha Kambhampati <ks...@gmail.com>.
Thanks Knut for the quick response.
Knut Anders Hatlen wrote:
>> <>This was a bug in the jdk. Fixed in build 97 or 98, I think.
>>
That explains the diff. The test was run with build 96.
>> <>
>
>>********* Diff file
>>testSetBinaryStreamLengthLessOnBlobTooLong(org.apache.derbyTesting.functionTests.tests.jdbc4.PreparedStatementTest)junit.framework.ComparisonFailure:
>>Unexpected SQL state. expected:<22001> but was:<58009> > FAILURES!!! >
>>
>I believe Andreas checked in a fix for this. Let's see... Yes,
>DERBY-1800.
>
>
>
Great!. Thanks.
Sunitha.
Re: jdk1.6 regresstion test failures: _Suite.junit and TestQueryObject
with IllegalAccessException
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
Sunitha Kambhampati <ks...@gmail.com> 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.
> ********* 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!
--
Knut Anders