-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8299813: java/nio/channels/DatagramChannel/Disconnect.java fails with jtreg test timeout due to lost datagram #19908
Conversation
👋 Welcome back dfuchs! A progress list of the required criteria for merging this PR into |
@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 69 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 |
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.
The changes look good to me.
Thanks @AlekseiEfimov ! If I don't receive further feedback I will integrate shortly |
/integrate |
Going to push as commit 49eb00d.
Your commit was automatically rebased without conflicts. |
Please find here a simple fix to solve an intermittent failure in java/nio/channels/DatagramChannel/Disconnect.java
On some platform, the underlying system may allow two datagram sockets to bind to the same port, if one of them uses the wildcard address and the other doesn't.
What happens here is that during DC:connect, if the socket is unbound, it will get bound to the wildcard.
From time to time, this results into binding to the same port that the
server
is using in the test.When that happens, datagram sent to the connected server may get misrouted and may not get delivered, and the call server::receive may block forever.
This change does two things:
This is rare, and skipping the receive part in that case does not invalidate the test.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/19908/head:pull/19908
$ git checkout pull/19908
Update a local copy of the PR:
$ git checkout pull/19908
$ git pull https://git.openjdk.org/jdk.git pull/19908/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 19908
View PR using the GUI difftool:
$ git pr show -t 19908
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/19908.diff
Webrev
Link to Webrev Comment