db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-2076) Rewrite junitTests/derbyNet/CompatibilityTest to conform to current JUnit usage
Date Fri, 29 Jun 2012 10:25:44 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403815#comment-13403815

Kristian Waagan commented on DERBY-2076:

Thanks, Knut.

I didn't notice the other test failing yesterday. But the error message looks similar:
"Caused by: org.apache.derby.client.am.SqlException: Java exception: 'org.apache.derbyTesting.functionTests.tests.lang.Price
: Bad version number in .class file: java.lang.ClassNotFoundException'."

I don't have the other error message in front of me now, but I think it mentioned the class
files versions (i.e. 49 and 50). Not sure if/how the above error is different. However, I
do see that the compile target in the new build.xml file is set to 1.6, which is probably
just a copy and paste error.
> Rewrite junitTests/derbyNet/CompatibilityTest to conform to current JUnit usage
> -------------------------------------------------------------------------------
>                 Key: DERBY-2076
>                 URL: https://issues.apache.org/jira/browse/DERBY-2076
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions:
>            Reporter: Andrew McIntyre
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-2076-0a-modernized_compat_test_preview.diff, derby-2076-0b-modernized_compat_test_preview.diff,
derby-2076-1a-initial.diff, derby-2076-1b-initial.diff
> The test org.apache.derbyTesting.functionTests.tests.junitTests.DerbyNet.CompatibilityTest
has been failing in the nightlies because it needs to be run in the old test harness, and
for some reason the property which grants permission to read ${user.home}/junit.properties
is not being picked up properly in the old harness. 
> I am able to resolve the problem by granting permission to read ${user.home}/junit.properties
to all, but the test should be refactored so that it can run with the rest of the junit tests
without needing the old harness.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message