|
Quick Lists
|
|
Bug ID:
|
6491461
|
|
Votes
|
0
|
|
Synopsis
|
TEST: java/lang/instrument .sh tests need to use $TESTVMOPTS in their java commands
|
|
Category
|
java:serviceability
|
|
Reported Against
|
|
|
Release Fixed
|
7(b26)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
6480566
|
|
Submit Date
|
08-NOV-2006
|
|
Description
|
Versions of jtreg older than this
http://javaweb/java/re/jct-tools/3.2.2_01/nightly/snapshot/
have a bug and do not pass TESTVMOPTS to shell scripts.
This has been fixed and the following jtreg tests should be changed
to use $TESTVMOPTS in their java commands:
java/lang/instrument/appendToClassLoaderSearch/CircularityErrorTest.sh
java/lang/instrument/appendToClassLoaderSearch/ClassUnloadTest.sh
java/lang/instrument/appendToClassLoaderSearch/run_tests.sh
java/lang/instrument/BootClassPath/BootClassPathTest.sh
java/lang/instrument/PremainClass/PremainClassTest.sh
Posted Date : 2006-11-08 21:21:52.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
The scripts appear to all use $JAVA or ${JAVA} to invoke
the java command for test execution. That makes all the
right places easy to find.
The one exception is the BootClassPath/BootClassPathTest.sh
which runs a Java program for both "setup" and "cleanup"
phases in addition to the execution phase. I don't think
that the setup or cleanup phases needs ${TESTVMOPTS}.
Posted Date : 2008-02-06 20:56:58.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
