-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8305847: Improve diagnosability and resilience of HttpClient::close tests #13426
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
Conversation
👋 Welcome back dfuchs! A progress list of the required criteria for merging this PR into |
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 Daniel, the changes look fine to me.
@dfuch 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 28 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 |
/integrate |
Going to push as commit 90b4006.
Your commit was automatically rebased without conflicts. |
The HttpClient close tests could be improved to provide better diagnosis.
The tests make some requests and register some dependent actions to check the response state, followed by some dependent action that will read the request body (from an input stream). But if the first dependent action asserts, the second will not be executed, and the body will neither be read or closed.
This will later prevent HttpClient::close method, or the HttpClient::awaitTermination method, to terminate as expected, and the test will then later fail in timeout (either from jtreg or awaitTermination). This behaviour can be confusing for failure analysis.
The tests could also be further simplified by creating the executor in which the responses bodies will eventually be read (called
readerService
) in thesetup()
method and later close it inteardown()
. This will simplify the cleanup phase, and ensure the service does not get closed until all dependent actions have been scheduled.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/13426/head:pull/13426
$ git checkout pull/13426
Update a local copy of the PR:
$ git checkout pull/13426
$ git pull https://git.openjdk.org/jdk.git pull/13426/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 13426
View PR using the GUI difftool:
$ git pr show -t 13426
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/13426.diff
Webrev
Link to Webrev Comment