Skip to content

Conversation

@cost0much
Copy link
Contributor

@cost0much cost0much commented Sep 3, 2024

Clean backport that makes TestListenerLeak more robust; already backported to 11, 17 and 21. Not clean because 8 file structure. Passes affected test on Linux x64.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • 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)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 574

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Sep 3, 2024

👋 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
Copy link

openjdk bot commented Sep 3, 2024

@cost0much This change now passes all automated pre-integration checks.

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

Reviewed-by: serb

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 37 new commits pushed to 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. Possible candidates are the reviewers of this PR (@mrserb) but any other Committer may sponsor as well.

➡️ 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 openjdk bot changed the title Backport f6be922952642f40dcf0d27b7896c9a6acdd6378 8316193: jdk/jfr/event/oldobject/TestListenerLeak.java java.lang.Exception: Could not find leak Sep 3, 2024
@openjdk
Copy link

openjdk bot commented Sep 3, 2024

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

@openjdk openjdk bot added the backport Port of a pull request already in a different code base label Sep 3, 2024
@cost0much cost0much marked this pull request as ready for review October 9, 2024 22:47
@openjdk openjdk bot added the rfr Pull request is ready for review label Oct 9, 2024
@mlbridge
Copy link

mlbridge bot commented Oct 9, 2024

Webrevs

@openjdk
Copy link

openjdk bot commented Oct 9, 2024

⚠️ @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
Copy link
Contributor Author

/approval request Improves the jfr TestListenerLeak test. Applies cleanly. Affected test passes. Risk is low: the change is test code only.

@openjdk
Copy link

openjdk bot commented Oct 9, 2024

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

@openjdk openjdk bot added the approval Requires approval; will be removed when approval is received label Oct 9, 2024
@bridgekeeper
Copy link

bridgekeeper bot commented Nov 7, 2024

@cost0much 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
Copy link

bridgekeeper bot commented Dec 5, 2024

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

@bridgekeeper bridgekeeper bot closed this Dec 5, 2024
@cost0much
Copy link
Contributor Author

/open

@openjdk openjdk bot reopened this Feb 4, 2025
@openjdk
Copy link

openjdk bot commented Feb 4, 2025

@cost0much This pull request is now open

@openjdk openjdk bot added ready Pull request is ready to be integrated and removed approval Requires approval; will be removed when approval is received labels Feb 4, 2025
@cost0much
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Feb 4, 2025
@openjdk
Copy link

openjdk bot commented Feb 4, 2025

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

@phohensee
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Feb 4, 2025

Going to push as commit 4c50940.
Since your change was applied there have been 37 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Feb 4, 2025
@openjdk openjdk bot closed this Feb 4, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Feb 4, 2025
@openjdk
Copy link

openjdk bot commented Feb 4, 2025

@phohensee @cost0much Pushed as commit 4c50940.

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

@cost0much cost0much deleted the JDK-8316193 branch February 4, 2025 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Port of a pull request already in a different code base integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants