The tier1 hotspot test group includes tier1_common which is:
tier1_common = \
sanity/BasicVMTest.java \
gtest/GTestWrapper.java \
gtest/LockStackGtests.java \
gtest/MetaspaceGtests.java \
gtest/LargePageGtests.java \
gtest/NMTGtests.java \
gtest/WindowsProcessorGroups.java
But tier5 testing runs group hotspot_misc which is defined as:
hotspot_misc = \
/ \
-applications \
-vmTestbase \
-:hotspot_compiler \
-:hotspot_gc \
-:hotspot_runtime \
-:hotspot_serviceability \
-:hotspot_containers
as this does not exclude gtest/* this means that the gtests in tier1_common are run under identical conditions in tier1 and tier5. This is a waste of testing resources.
Unclear what the right fix is. Maybe we need hotspot_gtest that gets included in tier1 and excluded from hotspot_misc?
Also note that the lists of gtests in tier1_common is only a subset of the available gtests.
tier1_common = \
sanity/BasicVMTest.java \
gtest/GTestWrapper.java \
gtest/LockStackGtests.java \
gtest/MetaspaceGtests.java \
gtest/LargePageGtests.java \
gtest/NMTGtests.java \
gtest/WindowsProcessorGroups.java
But tier5 testing runs group hotspot_misc which is defined as:
hotspot_misc = \
/ \
-applications \
-vmTestbase \
-:hotspot_compiler \
-:hotspot_gc \
-:hotspot_runtime \
-:hotspot_serviceability \
-:hotspot_containers
as this does not exclude gtest/* this means that the gtests in tier1_common are run under identical conditions in tier1 and tier5. This is a waste of testing resources.
Unclear what the right fix is. Maybe we need hotspot_gtest that gets included in tier1 and excluded from hotspot_misc?
Also note that the lists of gtests in tier1_common is only a subset of the available gtests.
- links to
-
Review(master) openjdk/jdk/25070