Skip to content

Conversation

@vish-chan
Copy link
Contributor

@vish-chan vish-chan commented Nov 27, 2025

This PR re-enables LocalRandom clinit after monitor pinning improvements.
Enabling this one would start printing random seeds, which is useful for test debugging.


Progress

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

Issue

  • JDK-8372652: Re-enable LocalRandom clinit after monitor pinning improvements (Enhancement - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28547

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Nov 27, 2025

👋 Welcome back vish-chan! 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
Copy link

openjdk bot commented Nov 27, 2025

@vish-chan 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:

8372652: Re-enable LocalRandom clinit after monitor pinning improvements

Reviewed-by: shade

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 218 new commits pushed to the master branch:

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 (@shipilev) 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
Copy link

openjdk bot commented Nov 27, 2025

@vish-chan To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command.

Applicable Labels
  • build
  • client
  • compiler
  • core-libs
  • graal
  • hotspot
  • hotspot-compiler
  • hotspot-gc
  • hotspot-jfr
  • hotspot-runtime
  • i18n
  • ide-support
  • javadoc
  • jdk
  • jmx
  • net
  • nio
  • security
  • serviceability
  • shenandoah

@vish-chan
Copy link
Contributor Author

/label hotspot

@openjdk
Copy link

openjdk bot commented Nov 27, 2025

@vish-chan
The hotspot label was successfully added.

@openjdk openjdk bot added the rfr Pull request is ready for review label Nov 27, 2025
@mlbridge
Copy link

mlbridge bot commented Nov 27, 2025

Webrevs

Copy link
Member

@shipilev shipilev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine to me. I suspect this one from @AlanBateman's Loom integration, maybe it was literally his addition? :)

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Nov 28, 2025
@shipilev
Copy link
Member

shipilev commented Nov 28, 2025

Also, you need to run the affected tests for extra safety. Looks like the entirety of vmTestbase needs to pass: make test TEST=vmTestbase/.

@AlanBateman
Copy link
Contributor

Looks fine to me. I suspect this one from @AlanBateman's Loom integration, maybe it was literally his addition? :)

JEP 425 had many contributors, here's the original commit in the loom repo in 2020 from Leonid:
openjdk/loom@d6a26a5

The recent work for JDK 26 allows virtual threads to preempt/unmount while waiting for another thread to initialize a class but they do not allow a virtual thread to unmount while executing a class initializer (as there are VM frames on the stack).

I think I would need more context to know if the change proposed here is okay.

@vish-chan
Copy link
Contributor Author

@shipilev jtreg:test/hotspot/jtreg/vmTestbase are passing locally.

@AlanBateman
Copy link
Contributor

You'll need to test with JTREG_TEST_THREAD_FACTORY=Virtual to see if there are issues.

@vish-chan
Copy link
Contributor Author

@AlanBateman I'm assuming running JTREG_TEST_THREAD_FACTORY=Virtual make test TEST=vmTestbase/ is enough?

@AlanBateman
Copy link
Contributor

@AlanBateman I'm assuming running JTREG_TEST_THREAD_FACTORY=Virtual make test TEST=vmTestbase/ is enough?

I'll defer to @lmesnik for guidance on this.

@lmesnik
Copy link
Member

lmesnik commented Nov 28, 2025

Unfortunately, there are might be failure of execution vmTestbase/withJTREG_TEST_THREAD_FACTORY=Virtual`. So it enough ensure the your fix doesn't create new failures and timeouts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hotspot [email protected] ready Pull request is ready to be integrated rfr Pull request is ready for review

Development

Successfully merging this pull request may close these issues.

4 participants