-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8291586: Broken links in JVMTI specification #10153
Conversation
👋 Welcome back sspitsyn! A progress list of the required criteria for merging this PR into |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not(ancestor::elide)
looks right. Looks good.
@sspitsyn 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:
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 42 new commits pushed to the
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. ➡️ To integrate this PR with the above commit message to the |
Thank you for review, Alan! |
I'm going to integrate this fix with one review as trivial. |
/integrate |
Going to push as commit 4067321.
Your commit was automatically rebased without conflicts. |
The Loom related spec of the extension VirtualThreadMount and VirtualThreadUnmount events in the jvmti.xml is surrounded by the elements
<elide> ... </elide>
, so these specs have to be ignored when thejvmti.html
is generated. However thejvmti.xsl
which does the XSL transformation misses to do that when the description of the JVM TI capabilities is collected.The fix is a one-liner:
The correctness verification both the generated
jvmti.html
andjvmti.h
was checked.TBD: mach5 sanity builds and
nsk.jvmti
tests runs.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10153/head:pull/10153
$ git checkout pull/10153
Update a local copy of the PR:
$ git checkout pull/10153
$ git pull https://git.openjdk.org/jdk pull/10153/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10153
View PR using the GUI difftool:
$ git pr show -t 10153
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10153.diff