-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8330814: Cleanups for KeepAliveCache tests #18884
Conversation
👋 Welcome back clanger! A progress list of the required criteria for merging this PR into |
@RealCLanger 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:
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 92 new commits pushed to the
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 |
@RealCLanger The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
Co-authored-by: Andrey Turbanov <turbanoff@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello Christoph, the latest changes look fine to me. I've added a trivial comment about reading the inputstream in one of the test, but you can leave it in its current form if you prefer to.
Please run tier2
tests once before integrating.
Thanks for the review. I added your suggestion. Will run it once more through our test suite tonight and then integrate tomorrow if all is good. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks reasonable. Give us some time to test that in our CI.
Our CI testing looks good. Please let me know when you are done. |
@dfuch May I merge now? |
If I don't hear back, I'll integrate tomorrow. Should we see problems later on, I'm available for following up. 😄 |
@RealCLanger sorry about that: I ran the tests then got distracted and forgot to come back. You're good to go - no issue found! |
Cool. Thanks for the confirmation. /integrate |
Going to push as commit a5005c8.
Your commit was automatically rebased without conflicts. |
@RealCLanger Pushed as commit a5005c8. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
While working in that area I found some potential for cleanup of a few tests.
Most notably:
B5045306.java:
B8291637.java:
KeepAliveTimerThread.java:
call to grp.destroy() at the end is pointless (API is void & deprecated for removal)
Generally:
The deprecated URL constructor is used. It can be switched to the handy URIBuilder
Some more try with resources here and there
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18884/head:pull/18884
$ git checkout pull/18884
Update a local copy of the PR:
$ git checkout pull/18884
$ git pull https://git.openjdk.org/jdk.git pull/18884/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18884
View PR using the GUI difftool:
$ git pr show -t 18884
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18884.diff
Webrev
Link to Webrev Comment