-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8322513: Build failure with minimal #17164
Conversation
👋 Welcome back xpbob! 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.
Looks fine and trivial.
Thanks
@xpbob 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 2 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the 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 (@dholmes-ora, @robehn) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
But I think you will then run into further problems due to JDK-8311218 - there is a "fatal" in jvm.cpp that will be called when JVM TI is not available. |
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.
Thanks, yes please ship now under trivial.
I have the same fix locally it working fine.
@dholmes-ora @robehn |
/integrate |
@dholmes-ora, minimal is used when you cross-compile, you need to build a minimal native buildjdk. Talking about the other issue: 8311218 |
/sponsor |
Going to push as commit 7db69e6.
Your commit was automatically rebased without conflicts. |
@DamonFool @xpbob Pushed as commit 7db69e6. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
@robehn I didn't realize Loom support was conditional. In any case the fatal is still wrong. |
Sorry, I just mean the bug you found in 8311218 would probably gone unnoticed for very long (at least for us). |
/backport jdk22 |
@dholmes-ora the backport was successfully created on the branch backport-dholmes-ora-7db69e6a in my personal fork of openjdk/jdk22. To create a pull request with this backport targeting openjdk/jdk22:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk22:
|
Build failure with minimal
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17164/head:pull/17164
$ git checkout pull/17164
Update a local copy of the PR:
$ git checkout pull/17164
$ git pull https://git.openjdk.org/jdk.git pull/17164/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17164
View PR using the GUI difftool:
$ git pr show -t 17164
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17164.diff
Webrev
Link to Webrev Comment