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 "Ole Solberg (JIRA)" <ji...@apache.org> on 2008/04/04 11:37:27 UTC
[jira] Updated: (DERBY-3588) suites.All fails to run on Jvm 1.5
when built with JDK 1.5 (Failed to invoke suite(): .jdbc4._Suite)
[ https://issues.apache.org/jira/browse/DERBY-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Solberg updated DERBY-3588:
-------------------------------
Attachment: suites.All_BuiltW15RunOn1.6.txt
BuildOn1.5_jdbc4._Suite_alt2.diff.txt
I have run .suites.All with the patch:
- BuildOn1.5_jdbc4._Suite_alt2: catching ClassNotFoundException.
This makes Derby/.suites.All built on JDK1.5 run OK on Jvm 1.4 and 1.5.
On JVM 1.6 .suites.All reports 'Tests run: 4186, Failures: 221, Errors: 80'.
See attachment 'suites.All_BuiltW15RunOn1.6.txt':
There were 80 errors:
1) testReEncrypt(org.apache.derbyTesting.functionTests.tests.jdbcapi.DboPowersTest)java.sql.SQLException: Connection authentication failure occurred. Reason: Invalid authentication..
.
.
There were 221 failures:
1) DRDAProtocolTest:clientjunit.framework.AssertionFailedError: java.lang.ClassNotFoundException: org.apache.derby.jdbc.EmbeddedDataSource40
.
.
I suppose we do not intend tests built on 1.5 to be run on 1.6, so this is as expected?
To do that we would have to detect at "addSuite / addTest" time, whether the Suite or Test built
on a "lower" JDK should be run with the current JVM.
Derby/.suites.All built on JDK 1.6 with this patch runs OK on 1.4, 1.5 and 1.6.
> suites.All fails to run on Jvm 1.5 when built with JDK 1.5 (Failed to invoke suite(): .jdbc4._Suite)
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-3588
> URL: https://issues.apache.org/jira/browse/DERBY-3588
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure, Test
> Affects Versions: 10.4.1.0, 10.5.0.0
> Environment: Building with JDK 1.5 ( 'j15lib=/usr/local/java/jdk1.5/jre/lib'.)
> Running tests with
> JVM:
> Sun Microsystems Inc.
> java version "1.5.0_14"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode)
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Attachments: BuildOn1.5_jdbc4._Suite_alt2.diff.txt, suites.All_BuiltW15RunOn1.6.txt
>
>
> I discovered that since svn r633968 - 2008-03-05 19:45:52 CET, .suites.All has failed with
> 'Failed to invoke suite():java.lang.ClassNotFoundException: org.apache.derbyTesting.functionTests.tests.jdbc4._Suite' in my test runs
> where I have built with JDK 1.5, i.e. have 'j15lib=/usr/local/java/jdk1.5/jre/lib' in ~/ant.properties.
> I think this is related to svn r633658 which removed the test for 'JDBC.vmSupportsJDBC4()' when doing
> 'suite.addTest(addSuiteByReflection("org.apache.derbyTesting.functionTests.tests.jdbc4._Suite"));'.
> I added the 'if (JDBC.vmSupportsJDBC4()){....}' again and am now runnning .suites.All on one of my 1.5 test platforms.
> An alternative might be to catch 'ClassNotFoundException' in 'addSuiteByReflection()'?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.