db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-3201) test SysinfoAPITest fails with weme6.1
Date Sat, 01 Jun 2013 11:48:20 GMT

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

Knut Anders Hatlen commented on DERBY-3201:

There has been no documented attempt to fix this in the 5 1/2 years that have passed since
the issue was reported. Myrna, do you think it would be OK to close the issue as Won't Fix
now that weme6.1 isn't supported any more on trunk?
> test SysinfoAPITest fails with weme6.1
> --------------------------------------
>                 Key: DERBY-3201
>                 URL: https://issues.apache.org/jira/browse/DERBY-3201
>             Project: Derby
>          Issue Type: Bug
>          Components: Test, Tools
>    Affects Versions:
>         Environment: weme6.1 (CDC Foundation 1.1 with JSR169 support)
>            Reporter: Myrna van Lunteren
>            Priority: Minor
>              Labels: derby_triage10_5_2
> Running the junit test tools.SysinfoAPITest with weme6.1 results in a failure:
> 1) testGetInfo(org.apache.derbyTesting.functionTests.tests.tools.SysinfoAPITest)junit.framework.ComparisonFailure:
expected:<------------------ Java Information ------------------> but was:<Java Version:
   J2ME Foundation Specification v1.1>
> 	at org.apache.derbyTesting.functionTests.tests.tools.SysinfoAPITest.testGetInfo(SysinfoAPITest.java:159)
> 	at java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:205)
> 	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:95)
> This has been aggravated by my change for DERBY-2903; after revision 593635 this failure
is now followed by:
> java.lang.IllegalStateException: File is closed
> 	at java.util.zip.ZipFile.getEntry(ZipFile.java:172)
> 	at java.util.jar.JarFile.getEntry(JarFile.java:309)
> 	at java.net.URLClassLoader.findResourceImpl(URLClassLoader.java:670)
> 	at java.net.URLClassLoader$5.run(URLClassLoader.java:604)
> 	at java.security.AccessController.doPrivileged(AccessController.java:213)
> 	at java.net.URLClassLoader.findResource(URLClassLoader.java:602)
> 	at java.lang.ClassLoader.getResource(ClassLoader.java:389)
> 	at java.lang.ClassLoader.getResource(ClassLoader.java:386)
> 	at java.lang.Class.getResource(Class.java:1086)
> 	at org.apache.derby.impl.tools.sysinfo.Main$5.run(Main.java:851)
> 	at java.security.AccessController.doPrivileged(AccessController.java:191)
> 	at org.apache.derby.impl.tools.sysinfo.Main.loadZipFromResource(Main.java:848)
> 	at org.apache.derby.impl.tools.sysinfo.Main.getAllInfo(Main.java:760)
> 	at org.apache.derby.impl.tools.sysinfo.Main.reportDerby(Main.java:220)
> 	at org.apache.derby.impl.tools.sysinfo.Main.getMainInfo(Main.java:120)
> 	at org.apache.derby.tools.sysinfo.getInfo(sysinfo.java:213)
> 	at org.apache.derbyTesting.functionTests.tests.tools.sysinfo_api_helper.run(SysinfoAPITest.java:188)
> However, the SysinfoAPITest is currently not running because of DERBY-2343, so I am not
going to undo the change for DERBY-2903 at this time.
> Still, some further research into this test, and the sysinfo API behavior is needed.
> Also, note that the test currently prints out a version number in testBuildNumber().

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message