JDK-7157738 : hotspot (CLOSED) test scripts not testing 64-bit JVM under JPRT/JTREG.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs23.6,hs24,7u65
  • Priority: P3
  • Status: Resolved
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2012-03-29
  • Updated: 2014-08-13
  • Resolved: 2014-08-13
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.
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.

We believe these are fixed in 7115383 and possibly other changes.

These issues don't affect 8 and 9 since: 1. test/closed/gc/4618940/Test4618940.sh and test/closed/gc/4785357/Test4785357.sh are solaris-sparc only tests. 2. 32-bit solaris-sparc is not supported by JDK 8 and JDK 9.

All should be fixed already. Need to verify and close this bug.

Most problems was fixed by Gary's changes for 7115383 and 8009152. I will do additional clean only of compiler tests for current bug.

Let's get this fixed for HS24, raising priority as well.