RFR: 8006164 [TESTBUG] compact profile hotspot test issues
david.holmes at oracle.com
Mon Aug 26 19:13:41 PDT 2013
On 27/08/2013 3:14 AM, Vladimir Kozlov wrote:
> Thank you, David
> For me it looks odd when you specify group as not other flags, like:
> Why it was designed this way?
Are you referring to the jtreg usage? ie
jtreg -jdk:xxx -v -r reportdir :compact1
The group is not an option it is a test designator similar to doing:
jtreg -jdk:xxx -v -r reportdir runtime/NMT gc/
> Can ou add jprt group too (as template for now)? We want for long time
> to run in JPRT small subset of our jtreg tests which will take less
> 15min. I know, it is separate problem but can you add it as template
> which we can use and extend later?
Adding this is trivial. The "template" would be:
There doesn't seem much point in me adding that at this time though.
Better to leave it until we know how it needs to be defined.
> On 8/25/13 6:45 PM, David Holmes wrote:
>> This change introduces the TEST.groups file to allow jtreg to run
>> regression tests by groups - where the groups are defined to support
>> testing of compact profiles and the minimal VM.
>> webrev: http://cr.openjdk.java.net/~dholmes/8006164/webrev/
>> The primary groups are:
>> - jdk
>> - jre
>> - compact3
>> - compact2
>> - compact2_minimal
>> - compact1
>> - compact1_minimal
>> The minimal VM is only supported on compact1 and compact2.
>> To select a group of tests you use :<group-name>
>> Eg to run only those tests that can run on compact1 use:
>> jtreg :compact1
>> Of course you still need to point jtreg at the right kind of runtime
>> image (and give it a full JDK as the compile-jdk!); and if testing the
>> minimal VM you need to tell jtreg to select it using
>> The full jtreg group facility is only available in the most recent jtreg
>> builds, so you will need to grab the latest nightly build, or latest
>> It is expected that these group definitions will need some tweaking. So
>> far testing has been limited to linux, but we want to get this in ASAP
>> to extend the testing.
>> Note: once this is in place, anyone writing regression tests will need
>> to be aware of whether that test is limited to certain profiles and
>> update the group file accordingly. Sometimes it is not the item being
>> tested that determines the minimum needed profile, but the test
>> infrastructure eg if it uses XML.
>> The changeset will be pushed via hotspot-embas that is what is used for
>> profile testing.
More information about the hotspot-dev