RFR: Loom test groups for development/porting use [v2]

Aleksey Shipilev shade at openjdk.java.net
Tue Oct 12 08:19:28 UTC 2021


On Tue, 12 Oct 2021 08:04:23 GMT, Alan Bateman <alanb at openjdk.org> wrote:

>> Aleksey Shipilev has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains one commit:
>> 
>>   Do separate test groups
>
> test/hotspot/jtreg/TEST.groups line 111:
> 
>> 109:   :tier1_loom \
>> 110:   runtime/jni/IsVirtualThread \
>> 111:   serviceability/dcmd/thread
> 
> It would be okay to include these in tier1_loom_runtime and tier1_loom_serviceability as you had them.

Fixed, see new commit.

> test/jdk/TEST.groups line 105:
> 
>> 103:     java/util/concurrent/Future \
>> 104:     jdk/internal/vm/Continuation \
>> 105:     jdk/jfr/threading
> 
> Probably better to run java/util/concurrent rater than specific directories, it will otherwise get unwieldy once the tests move to the right place. You can probably drop Throwable, it's not interesting to run have its tests in this test group. Not sure about the JFR threading tests, we've been using the jdk_jfr group for that.

Fixed. I'd like to have JFR "thread" tests in this group to test thread events.

-------------

PR: https://git.openjdk.java.net/loom/pull/74


More information about the loom-dev mailing list