db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ahsan shamsudeen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-2343) sysinfo API only returns correct information for the first jar file on the classpath
Date Tue, 20 Aug 2013 07:38:52 GMT

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

ahsan shamsudeen commented on DERBY-2343:
-----------------------------------------

According to code coverage analysis of EMMA and Jacoco, org.apache.derby.tools.sysinfo has
a poor code coverage.

But , Derby has test for this class in  org.apache.derbyTesting.functionTests.tests.tools.SysinfoAPITest.
So, the problem is this test are not taken into account by coverage suites.

When I run the unit test for SysinfoAPITest, it throws following message 
svn: E155036: Working copy '\Workspace\derby' is too old (format 9, created by Subversion
1.5)

But, Derby currently released Apache Subversion 1.8.1. Does this cause any issues ? 

Thanks,
Ahsan


 
                
> sysinfo API only returns correct information for the first jar file on the classpath
> ------------------------------------------------------------------------------------
>
>                 Key: DERBY-2343
>                 URL: https://issues.apache.org/jira/browse/DERBY-2343
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.1.4
>            Reporter: Andrew McIntyre
>            Priority: Trivial
>              Labels: derby_triage10_5_2
>
> While updating the sysinfo_api test to our current JUnit usage, I rediscovered the problem
which has kept this test from running on a regular basis: when running the test from jar files,
only the first jar file on the classpath properly reports its information through the sysinfo
API.
> It is not a security manager issue, as disabling the security manager did not solve the
problem. There may be jar-sealing issues involved, but I haven't looked into the issue very
deeply. Just noting the issue here for later investigation.
> I will commit a patch which updates the current sysinfo_api test to be called SysinfoAPITest,
and also add a note to tools._Suite about the problem.

--
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

Mime
View raw message