7403: Fix JFR Parser struct types hashcode

[thegreystone]

---

Progress

• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JMC-7403: Fix JFR Parser struct types hashcode

Reviewers

• Jaroslav Bachorik (@jbachorik - Author)
• Jean-Philippe Bempel (@jpbempel - Committer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jmc pull/313/head:pull/313
$ git checkout pull/313

Update a local copy of the PR:
$ git checkout pull/313
$ git pull https://git.openjdk.java.net/jmc pull/313/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 313

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jmc/pull/313.diff

[bridgekeeper]

👋 Welcome back hirt! 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.

[mlbridge]

Webrevs

• 00: Full (60e5b62c)

[openjdk]

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

7403: Fix JFR Parser struct types hashcode

Reviewed-by: jbachorik, jpbempel

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:

• fea3787: 7415: Fix Maven prerequisite in README
• 14b8357: 7414: Avoid volatile writes from Atomics default values
• 085a4a6: 7413: Fix building JMC with Docker

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.

[thegreystone]

/integrate

[openjdk]

Going to push as commit 90165cf.
Since your change was applied there have been 5 commits pushed to the master branch:

• 4d413ee: 7411: GPG signing in Github action fails
• 01fb898: 7412: Update the jacoco maven plugin
• fea3787: 7415: Fix Maven prerequisite in README
• 14b8357: 7414: Avoid volatile writes from Atomics default values
• 085a4a6: 7413: Fix building JMC with Docker

Your commit was automatically rebased without conflicts.

[openjdk]

@thegreystone Pushed as commit 90165cf.

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