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
7903214: JOL: Complete some TODOs in VMOptions #29
Conversation
👋 Welcome back SteafanMrZhou! A progress list of the required criteria for merging this PR into |
Webrevs
|
Can you also please go to https://github.com/SteafanMrZhou/jol/actions/ -- and check that workflows are enabled? The PRs need to be tested, and workflows are supposed to run automatically. |
The tested has completed,thanks. |
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.
Ah, now I remember why these are not printed. On 32-bit VMs, where the options are not available, it would print unnecessary noise:
# WARNING: Unable to get compressed oops. java.lang.IllegalArgumentException: VM option "UseCompressedOops" does not exist
# WARNING: Unable to get compressed class pointersjava.lang.IllegalArgumentException: VM option "UseCompressedClassPointers" does not exist
# WARNING: Unable to get compressed oops. java.lang.IllegalArgumentException: VM option "UseCompressedOops" does not exist
# WARNING: the compressed oops is unavailable
# Running 32-bit HotSpot VM.
# Objects are 8 bytes aligned.
# ref, bool, byte, char, shrt, int, flt, lng, dbl
# Field sizes: 4, 1, 1, 2, 2, 4, 4, 8, 8
# Array element sizes: 4, 1, 1, 2, 2, 4, 4, 8, 8
# Array base offsets: 12, 12, 12, 12, 12, 12, 12, 16, 16
...
These warnings cannot be reasonably fixed by users, so there is no point in printing them.
I suggest we just drop the // TODO:
lines in this patch, and move on.
Alright,I changed for a later.just wait a minute. |
|
@SteafanMrZhou This change now passes all automated pre-integration checks. 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 no new commits pushed to 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 (@shipilev) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Why can't PRs be merged, but integrated? |
/integrate |
@SteafanMrZhou |
Bots are handling all integrations to perform checks, do proper metadata updates, etc. This is how OpenJDK infra works. |
How to become a Committer of this project?Thanks a lot. |
/sponsor |
Going to push as commit 9fd21c9. |
@shipilev @SteafanMrZhou Pushed as commit 9fd21c9. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The same way as for the rest of OpenJDK and other OSS projects: accrue a track record of good contributions, reviews, involvement. |
I'm sorry about the last commit, I forgot to update my branch.
I have updated the branch synchronously, please check the PR,thanks a lot.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jol pull/29/head:pull/29
$ git checkout pull/29
Update a local copy of the PR:
$ git checkout pull/29
$ git pull https://git.openjdk.org/jol pull/29/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 29
View PR using the GUI difftool:
$ git pr show -t 29
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jol/pull/29.diff