[ http://issues.apache.org/jira/browse/DERBY-1091?page=all ]
Myrna van Lunteren updated DERBY-1091:
--------------------------------------
Attachment: DERBY-1091_20060702.stat
DERBY-1091_20060702.diff
Attaching a patch - DERBY-1091_20060702.* - which:
- as planned leaves testJavaFlags and testSpecialProps unchanged, except for
correcting some illogical reference to testflags in RunSuite; leaves the
<test>_app.properties in place; makes jvmflags a '^' separated list rather than
a space-separated list as a propertyvalue, which gets converted into a
space-separated list in the local variable in RunTest.java.; modify padding
with 'D'to only when there is no '-' ; make the command line flags be passed
after the suite flags and the suite flags after the test flags, so that the jvm
follows the desired precedence of commandline-suite-test because the jvm
(supposedly) picks up the 'last' setting; adjust NetServer and RunTest to check
for -Xmx and -Xms as well as -mx and -ms
- in addition modified README.htm to document this
- modified the test properties files where jvmflags was used.
I would appreciate it if people that use/need to use specific jvmflags in their
testing could verify this patch works as expected.
Note: derbyall passed on linux - except for some odd
java.util.PropertyPermission read errors on user.dir, which appear to be
related to the jvm release I was running (ibm 142 build cxia32142-20060421
(SR5)). At least these failing (store) tests passed when run with sun's jdk 142
or an older ibm 142 build...
> Test harness does not pass jvm flags properly if there are more than 1
> property in jvm flags
> --------------------------------------------------------------------------------------------
>
> Key: DERBY-1091
> URL: http://issues.apache.org/jira/browse/DERBY-1091
> Project: Derby
> Type: Test
> Components: Test
> Versions: 10.2.0.0
> Environment: Windows 2000
> Reporter: Ramandeep Kaur
> Assignee: Myrna van Lunteren
> Priority: Minor
> Attachments: DERBY-1091_20060702.diff, DERBY-1091_20060702.stat
>
> To run Derby tests with EMMA for Code coverage, there is a need to set up
> emma flag -Djvmflags=-Demma.verbosity.level=silent. This is basically to
> enable EMMA not to print out any messages to avoid having any diffs. This all
> works fine when running Derby tests with EMMA for jdk142, jdk15, jdk131 etc
> because there is no other jvm flag that is passed while calling RunSuite
> Command.
> Now, while running tests with j2me/cdc/foundation, another value needs to be
> passed as jvmflag which is
> -Djvmflags="Dij.dataSource=org.apache.derby.jdbc.EmbeddedSimpleDataSource".
> I tried to combine values for both jvm flags as following, but it did not
> work properly:
> 1. -Djvmflags='-Demma.verbosity.level=silent
> -Dij.dataSource=org.apache.derby.jdbc.EmbeddedSimpleDataSource'
> During this run, the value that was further passed while running one test was
> Djvmflags="'-Demma.verbosity.level=silent".
> As you can notice it took jvm flag as '-Demma.verbosity.level=silent
> 2. -Djvmflags="-Demma.verbosity.level=silent
> -Dij.dataSource=org.apache.derby.jdbc.EmbeddedSimpleDataSource"
> During this run, the value that was further passed while running one test was
> Djvmflags=""-Demma.verbosity.level=silent".
> As you can notice it took jvm flag as "-Demma.verbosity.level=silent
> From the above it looks like test harness needs to be changed so that it can
> parse multiple values for jvm flags properly.
--
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
