-
Bug
-
Resolution: Fixed
-
P4
-
hs24
-
b12
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2225115 | 8 | Kevin Walls | P4 | Resolved | Fixed | b41 |
| JDK-8018227 | 7u45 | Kevin Walls | P4 | Closed | Fixed | b01 |
| JDK-8002507 | 7u40 | Kevin Walls | P4 | Closed | Fixed | b01 |
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:
test/compiler/6894807/Test6894807.sh
test/runtime/6626217/Test6626217.sh
test/runtime/6878713/Test6878713.sh
test/runtime/7020373/Test7020373.sh
test/runtime/7051189/Xchecksig.sh
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:
test/compiler/6894807/Test6894807.sh
test/runtime/6626217/Test6626217.sh
test/runtime/6878713/Test6878713.sh
test/runtime/7020373/Test7020373.sh
test/runtime/7051189/Xchecksig.sh
- backported by
-
JDK-2225115 hotspot test scripts not testing 64-bit JVM under JPRT/JTREG.
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-