[ http://issues.apache.org/jira/browse/DERBY-892?page=all ]
Andrew McIntyre reopened DERBY-892:
-----------------------------------
Reopening this issue due to a problem with the test harness. There is some sort
of race-type condition whereby the test harness does not have the necessary
setIO permission to reassign the system out and err streams when the nist suite
is run as a subsuite of derbyall in useprocess=false mode. The error does not
occur when running the nist suite separately. I haven't had time to analyze the
problem completely, but I'm guessing that we've set a security manager for the
test harness code without the setIO permissions in the policy file in effect at
the time, but the setIO permission needed for running in useprocess=false mode
has not been granted to the test harness by the policy file currently in
effect. Reinstated blanket setIO and setSecurityManager permissions for the
test harness in derby_tests.policy with revision 409565. Full stack trace that
appears in the top-level execution of derbyall below:
*** Start: schema1 jdk1.5.0_02 derbyall:nist 2006-05-25 21:54:46 ***
Exception in thread "main" java.security.AccessControlException: access denied
(java.lang.RuntimePermission setIO)
at
java.security.AccessControllerContext.checkPermission(AccessControlContext.java:264)
at
java.security.AccessController.checkPermission(AccessController.java:427)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
at java.lang.System.checkIO(System.java:207)
at java.lang.System.setOut(System.java:147)
at
org.apache.derbyTesting.functionTests.harness.RunTest.execTestNoProcess(RunTest.java:2552)
at
org.apache.derbyTesting.functionTests.harness.RunTest.testRun(RunTest.java:493)
at
org.apache.derbyTesting.functionTests.harness.RunTest.main(RunTest.java:352)
at
org.apache.derbyTesting.functionTests.harness.RunList.runTests(RunList.java:575)
at
org.apache.derbyTesting.functionTests.harness.RunList.runSuites(RunList.java:310)
at
org.apache.derbyTesting.functionTests.harness.RunList.<init>(RunList.java:164)
at
org.apache.derbyTesting.functionTests.harness.RunSuite.getSuitesList(RunSuite.java:208)
at
org.apache.derbyTesting.functionTests.harness.RunSuite.main(RunSuite.java:147)
> add mechanism for specifying policy file for individual function tests
> ----------------------------------------------------------------------
>
> Key: DERBY-892
> URL: http://issues.apache.org/jira/browse/DERBY-892
> Project: Derby
> Type: Bug
> Components: Test
> Versions: 10.2.0.0
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: DERBY-892_20060514.diff, DERBY-892_20060514.stat,
> DERBY-892_3_20060523.diff, DERBY-892_3_20060523.stat,
> DERBY-892_4_20060523.diff, DERBY-892_4_20060523.stat, derby-892_pre.diff
>
> It would be nice to be able to specify a test-specific policy file.
> This should get handled similar to existing properties, i.e. get specified in
> a test_app.properties file (or, for a suite, in the suite.properties file).
> The file should then be copied into the correct place.
> Note, that the 'old' functionTests harness (as opposed to junit tests)
> includes a check for a property called 'serverPolicyFile' (in
> harness/jvm.java). The name is a left over from when the policy file was only
> used for/by network server, and should be renamed - derbyTestPolicyFile, for
> instance. It is not used anywhere at present, and not specific to network
> server. It would be nice if this could be expanded, or, if not used, removed.
> The default policy file used is the derby_tests.policy file under
> functionTests/util.
> Also, currently, the property can only be used with RunTest - for further
> traction, it should probably get passed on through RunSuite/RunList.
> Once confirmed to be working, the property should get documented in
> <trunk>/java/testing/README.htm.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
