8382275: Update nsk/stress/jni to use ThreadWrapper

[shivshah-oracle]

Changed jnistress001-007, JNIter classes, and GarbageGenerator to extend ThreadWrapper instead of Thread. Interrupter left as platform thread since it only interrupts other threads and doesn't do test work.

• I confirm that I make this contribution in accordance with the OpenJDK Interim AI Policy.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed (2 reviews required, with at least 1 Reviewer, 1 Author)

Issue

• JDK-8382275: Update nsk/stress/jni to use ThreadWrapper (Sub-task - P4)

Reviewers

• Leonid Mesnik (@lmesnik - Reviewer)
• SendaoYan (@sendaoYan - Committer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/30795/head:pull/30795
$ git checkout pull/30795

Update a local copy of the PR:
$ git checkout pull/30795
$ git pull https://git.openjdk.org/jdk.git pull/30795/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 30795

View PR using the GUI difftool:
$ git pr show -t 30795

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/30795.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back shivshah-oracle! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@shivshah-oracle This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8382275: Update  nsk/stress/jni to use ThreadWrapper

Reviewed-by: lmesnik, syan

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 78 new commits pushed to the master branch:

• af40ceb: 8382529: Tests com/sun/jdi/RedefineCrossEvent.java and com/sun/jdi/ClassesByName2Test.java fail when running frequent GC
• 2deae27: 8382501: Rename occurrences of com.sun.hotspot.perfdata in HotSpot source code
• f97effa: 8381993: Simplify MetaspaceClosure handling of Array and GrowableArray
• ... and 75 more: https://git.openjdk.org/jdk/compare/10e23dd5823258cfbf500175dde23be12cdd99bf...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@lmesnik, @sendaoYan) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[openjdk]

@shivshah-oracle The following label will be automatically applied to this pull request:

• hotspot-runtime

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[openjdk]

The total number of required reviews for this PR has been set to 2 based on the presence of this label: hotspot-runtime. This can be overridden with the /reviewers command.

[mlbridge]

Webrevs

• 00: Full (28d51303)

[sendaoYan]

Hi, how do we verify the correctness of this change. Run the touched tests by virtual thread and default thread is sufficient or not

[shivshah-oracle]

Hi, how do we verify the correctness of this change. Run the touched tests by virtual thread and default thread is sufficient or not

Ran all 7 on mach5 with and without TEST_THREAD_FACTORY=Virtual, all platforms pass. Running with TEST_THREAD_FACTORY=Virtual proves the tests actually run on virtual threads now which is the whole point of the change and running without proves we didn’t break existing behavior. That’s the verification.. both thread types work.

[lmesnik]

I think it is enough to verify that tests passed in the default mode and with virtual threads.
The threads are transparent and testing in the most cases should just work.

[sendaoYan]

LGTM