Myrna van Lunteren (JIRA) wrote:
[ https://issues.apache.org/jira/browse/DERBY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574808#action_12574808 ]
Myrna van Lunteren commented on DERBY-2109:
-------------------------------------------
I think one or more of the commits may have caused weme6.1 (my J2ME/JSR169
implementation) to run into 152 failed tests in derbyall.
The last one in the report for example has a failure diff like so:
====================
*** Start: T_MarkedLimitInputStream jdkJ2ME Foundation Specification v1.1
derbyall:unit 2008-03-01 07:05:44 ***
1 del
< -- Unit Test T_MarkedLimitInputStream starting
2 del
< -- Unit Test T_MarkedLimitInputStream finished
2 add
Parsing policy file:
file:C:/jartest/JarResults.2008-02-29/weme6.1_derbyall/derby_tests.policy,
found unexpected: permission
xxxxxxFILTERED-TIMESTAMPxxxxxGMT Thread[main,5,main]
java.security.AccessControlException: Access denied (java.io.FilePermission
derby.log read)
xxxxxxFILTERED-TIMESTAMPxxxxxGMT Thread[main,5,main] Cleanup action starting
ERROR XBM02: Startup failed due to missing functionality for
org.apache.derbyTesting.unitTests.harness.UnitTestManager. Please ensure your
classpath includes the correct Derby software.
Cleanup action completed
xxxxxxFILTERED-TIMESTAMPxxxxxGMT Thread[main,5,main]
xxxxxxFILTERED-TIMESTAMPxxxxxGMT Thread[main,5,main] Startup failed due to
missing functionality for
org.apache.derbyTesting.unitTests.harness.UnitTestManager. Please ensure your
classpath includes the correct Derby software.
ERROR XBM02: Startup failed due to missing functionality for
org.apache.derbyTesting.unitTests.harness.UnitTestManager. Please ensure your
classpath includes the correct Derby software.
Test Failed.
=================
I understood from the discussion re DERBY-3445 that with this jvm I need to run with
properties spelled out (so I'm now running with -Demma.active=""). Is there
some property I need to specify for these changes too that I missed?
Any other suggestions?
The workaround discussed in DERBY-3445 was for running junit tests.
While the same workaround is needed for the old harness, it has to be
implemented within the harness as it kicks off the virtual machine to
run the test. Around line 401 of jvm.java there is code that sets the
other properties that are used by the harness, I wonder if emma.active
is needed here as well.
Dan.
