JDK-7157734 : hotspot test scripts not testing 64-bit JVM under JPRT/JTREG.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: test
  • Affected Version: hs24
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2012-03-29
  • Updated: 2013-06-26
  • Resolved: 2012-05-26
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 JDK 8 Other
7u40Fixed 8Fixed hs24Fixed
Related Reports
Relates :  
Some hotspot testcase scripts check for a file JDK64BIT in the home directory, and 
use the contents as command-line arguments to the JVM.  Without this they never
test 64-bit mode (at least on Solaris).

The JDK6BIT file's contents are expected to be -d64 to ensure the 64-bit 
JDK is executed.

JPRT does not use this file convention, so some tests are not testing
64-bit mode.

The scripts should use TESTVMOPTS instead, which jtreg sets.  This will
contain -d64 when JPRT/JTREG is testing a 64-bit JVM.

Files in hotspot/test needing changes:


EVALUATION http://hg.openjdk.java.net/lambda/lambda/hotspot/rev/037973617842

EVALUATION http://hg.openjdk.java.net/hsx/hotspot-main/hotspot/rev/037973617842

EVALUATION http://hg.openjdk.java.net/hsx/hotspot-rt/hotspot/rev/037973617842

EVALUATION http://cr.openjdk.java.net/~kevinw/7157734/webrev.02/