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-6079) 100's of errors in nightly test run on weme after jacoco property/priviledges checkin
Date Wed, 20 Feb 2013 19:51:14 GMT

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

Kristian Waagan commented on DERBY-6079:
----------------------------------------

KM> So I assume that means weme runs now need both -Djacoco.active="" and -Demma.active=""
is that correct?

It depends.

More detailed:
With patch 1a you need to run with both properties set.
The intention of patch 2a was to make it possible to run on weme without specifying any of
the two properties.
I believe Myrna has confirmed that patch 2a worked for the JUnit tests.

My patches on this issue didn't change anything for derbyall, only suites.All (or any other
junit test/suite).
I think Myrna is checking the status for derbyall.

I can't remember if I added any support for JaCoCo coverage for the tests in derbyall. If
there are no more issues, it means that we can remove references to both emma.active and jacoco.active
going forward.

                
> 100's of errors in nightly test run on weme after jacoco property/priviledges checkin
> -------------------------------------------------------------------------------------
>
>                 Key: DERBY-6079
>                 URL: https://issues.apache.org/jira/browse/DERBY-6079
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.10.0.0
>         Environment: weme6.2
> Windows XP - x86 - 5.1 build 2600 Service Pack 3
>            Reporter: Mike Matrigali
>         Attachments: derby-6079-1a-propagate_jacocoactive_j9.diff, derby-6079-2a-set_props_j9.diff
>
>
> 100's of errors in nightly test, all seem to be a null pointer while processing policy
files during setup. 
> problem is in jvm code, and it seems specific to the weme6.2 jvm.
> The only change being tested in this run was 
>  For instance:
> 330) testAll(org.apache.derbyTesting.functionTests.tests.lang.NativeAuthenticationServiceTest)java.lang.NullPointerException
> 	at com.ibm.oti.util.DefaultPolicy.addGrant(DefaultPolicy.java:619)
> 	at com.ibm.oti.util.DefaultPolicy.readPolicy(DefaultPolicy.java:608)
> 	at com.ibm.oti.util.DefaultPolicy.getSystemPolicy(DefaultPolicy.java:922)
> 	at com.ibm.oti.util.DefaultPolicy.getPermissionsImpl(DefaultPolicy.java:114)
> 	at com.ibm.oti.util.DefaultPolicy$1.run(DefaultPolicy.java:67)
> 	at java.security.AccessController.doPrivileged(AccessController.java:204)
> 	at com.ibm.oti.util.DefaultPolicy.privateGetPermissions(DefaultPolicy.java:65)
> 	at com.ibm.oti.util.DefaultPolicy.getPermissions(DefaultPolicy.java:53)
> 	at java.security.Policy.getPermissions(Policy.java:131)
> 	at java.security.ProtectionDomain.implies(ProtectionDomain.java:177)
> 	at java.security.AccessController.checkPermission(AccessController.java:99)
> 	at java.lang.SecurityManager.checkPermission(SecurityManager.java:534)
> 	at java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:331)
> 	at java.lang.System.getProperty(System.java:384)
> 	at java.lang.System.getProperty(System.java:366)
> 	at org.apache.derbyTesting.junit.BaseTestCase$3.run(BaseTestCase.java:292)
> 	at java.security.AccessController.doPrivileged(AccessController.java:204)
> 	at org.apache.derbyTesting.junit.BaseTestCase.getSystemProperty(BaseTestCase.java:288)
> 	at org.apache.derbyTesting.junit.DropDatabaseSetup.removeDatabase(DropDatabaseSetup.java:86)
> 	at org.apache.derbyTesting.junit.TestConfiguration$5.tearDown(TestConfiguration.java:868)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> Here is link to all errors:
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/weme6.2/1447575-suites.All_diff.txt
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/weme6.2/1447575-derbyall_diff.txt

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