Skip to content
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.
/ jdk16u Public archive

8261334: NMT: tuning statistic shows incorrect hash distribution #42

Closed
wants to merge 1 commit into from

Conversation

hseigel
Copy link
Member

@hseigel hseigel commented Feb 25, 2021

The original bug fix patch applied cleanly. After applying the patch to a JDK-16u repo, the fix was regression tested by running Mach5 tiers 1 and 2 on Linux, Windows, and Mac OS, and running tiers 3-5 on Linux x64.


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change must be properly reviewed

Issue

  • JDK-8261334: NMT: tuning statistic shows incorrect hash distribution

Download

$ git fetch https://git.openjdk.java.net/jdk16u pull/42/head:pull/42
$ git checkout pull/42

@bridgekeeper
Copy link

bridgekeeper bot commented Feb 25, 2021

👋 Welcome back hseigel! 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 openjdk bot changed the title Backport 20d7713c57d312e7f196f6887666c195f00da99c 8261334: NMT: tuning statistic shows incorrect hash distribution Feb 25, 2021
@openjdk
Copy link

openjdk bot commented Feb 25, 2021

This backport pull request has now been updated with issue from the original commit.

@openjdk
Copy link

openjdk bot commented Feb 25, 2021

@hseigel 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:

8261334: NMT: tuning statistic shows incorrect hash distribution

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

  • 262c989: 8260029: aarch64: fix typo in verify_oop_array
  • c000594: 8261522: [PPC64] AES intrinsics write beyond the destination array
  • 5c130eb: 8261585: Restore HandleArea used in Deoptimization::uncommon_trap

Please see this link for an up-to-date comparison between the source branch of this pull request and 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.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot added ready Pull request is ready to be integrated rfr Pull request is ready for review labels Feb 25, 2021
@hseigel
Copy link
Member Author

hseigel commented Feb 25, 2021

/integrate

@openjdk openjdk bot closed this Feb 25, 2021
@openjdk openjdk bot added integrated Pull request has been integrated and removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Feb 25, 2021
@openjdk
Copy link

openjdk bot commented Feb 25, 2021

@hseigel Since your change was applied there have been 3 commits pushed to the master branch:

  • 262c989: 8260029: aarch64: fix typo in verify_oop_array
  • c000594: 8261522: [PPC64] AES intrinsics write beyond the destination array
  • 5c130eb: 8261585: Restore HandleArea used in Deoptimization::uncommon_trap

Your commit was automatically rebased without conflicts.

Pushed as commit 9fa0e03.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@mlbridge
Copy link

mlbridge bot commented Feb 25, 2021

Webrevs

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport clean integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

1 participant