8295: Shutdown event type id is not properly translated for Oracle JDK 8

[thegreystone]

The conversion from the legacy jfr 0.9 id wasn't happening for the VM shutdown event.

---

Progress

• Commit message must refer to an issue
• Change must be properly reviewed (1 review required, with at least 1 Committer)

Issue

• JMC-8295: Shutdown event type id is not properly translated for Oracle JDK 8 (Bug - P4)

Reviewers

• Virag Purnam (@viragpurnam - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jmc.git pull/614/head:pull/614
$ git checkout pull/614

Update a local copy of the PR:
$ git checkout pull/614
$ git pull https://git.openjdk.org/jmc.git pull/614/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 614

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jmc/pull/614.diff

Using Webrev

Link to Webrev Comment

[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.

[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:

8295: Shutdown event type id is not properly translated for Oracle JDK 8

Reviewed-by: vpurnam

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 1 new commit pushed to the master branch:

• cbf7349: 8298: Update to Eclipse 2024-09

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.

[mlbridge]

Webrevs

• 00: Full (177bb4c5)

[thegreystone]

/integrate

[openjdk]

Going to push as commit 254d795.
Since your change was applied there has been 1 commit pushed to the master branch:

• cbf7349: 8298: Update to Eclipse 2024-09

Your commit was automatically rebased without conflicts.

[openjdk]

@thegreystone Pushed as commit 254d795.

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