8258734: jdk/jfr/event/oldobject/TestClassLoaderLeak.java failed with "RuntimeException: Could not find class leak"

[amosshi]

Directory "build/jtreg-test" not found: creating
Directory "JTreport" not found: creating
Passed: jdk/jfr/event/oldobject/TestClassLoaderLeak.java
Test results: passed: 1
Report written to /Users/I048686/SAPDevelop/github.com/dev-8258734-17/JTreport/html/report.html
Results written to /Users/I048686/SAPDevelop/github.com/dev-8258734-17/build/jtreg-test

---

Progress

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

Issue

• JDK-8258734: jdk/jfr/event/oldobject/TestClassLoaderLeak.java failed with "RuntimeException: Could not find class leak" (Bug - P4)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 2929

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

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

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[openjdk]

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

[openjdk]

⚠️ @amosshi 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.

[mlbridge]

Webrevs

• 00: Full (b43291c6)

[bridgekeeper]

@amosshi This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[bridgekeeper]

@amosshi This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the /open pull request command.