JDK-6491461 : TEST: java/lang/instrument .sh tests need to use $TESTVMOPTS in their java commands
  • Type: Bug
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2006-11-08
  • Updated: 2012-10-01
  • Resolved: 2011-03-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7 b26Fixed
Related Reports
Relates :  
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

Comments
SUGGESTED FIX See attached 6491461-webrev-cr0 file for the proposed fix.
07-02-2008

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}.
06-02-2008

SUGGESTED FIX Add ${TESTVMOPTS} (no quotes) to almost all invocations of the java cmd.
06-02-2008