8316193: jdk/jfr/event/oldobject/TestListenerLeak.java java.lang.Exception: Could not find leak

[cost0much]

Clean backport; already backported to 21. Improves jdk/jfr/event/oldobject/TestListenerLeak test making it more robust. Passes affected test.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8316193 needs maintainer approval

Issue

• JDK-8316193: jdk/jfr/event/oldobject/TestListenerLeak.java java.lang.Exception: Could not find leak (Bug - P4 - Approved)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/2821/head:pull/2821
$ git checkout pull/2821

Update a local copy of the PR:
$ git checkout pull/2821
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/2821/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 2821

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/2821.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back cost0much! 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]

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

8316193: jdk/jfr/event/oldobject/TestListenerLeak.java java.lang.Exception: Could not find leak

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:

• be4f913: 8312049: runtime/logging/ClassLoadUnloadTest can be improved

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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[openjdk]

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

[openjdk]

⚠️ @cost0much This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[cost0much]

/approval request Improves the test added in JDK 22. Applies cleanly. Affected test passes. Risk is low: the change is test code only.

[openjdk]

@cost0much
8316193: The approval request has been created successfully.

[mlbridge]

Webrevs

• 00: Full (c01da060)

[cost0much]

/integrate

[openjdk]

@cost0much
Your change (at version c01da06) is now ready to be sponsored by a Committer.

[Rudometov]

/sponsor

[openjdk]

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

• be4f913: 8312049: runtime/logging/ClassLoadUnloadTest can be improved

Your commit was automatically rebased without conflicts.

[openjdk]

@Rudometov @cost0much Pushed as commit 97e4a93.

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