-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
8301457: Code in SendPortZero.java is uncommented even after JDK-8236852 was fixed #14952
Conversation
👋 Welcome back michaelm! A progress list of the required criteria for merging this PR into |
@Michael-Mc-Mahon 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
|
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 fine to me.
You might want to change the last modification years in both copyright headers.
// wildcard addr w/valid port | ||
// Referenced in bug 8236105, but not addressed. | ||
// So, this scenario is not tested |
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.
Is this scenario planned to be addressed? If there is a bug for that (JDK-8236807?) then it could be mentioned in this comment.
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.
That bug looks like the same issue. I will add a comment to the code and a note in the bug report about the test.
wildcardValidPkt.setAddress(addr); | ||
wildcardValidPkt.setPort(socket.getLocalPort()); | ||
*/ | ||
wildcardValidPkt.setAddress(wildcardAddr); |
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.
you have enabled setup code, but not enabled its coresponding test scenario. Is that intentional?
@Michael-Mc-Mahon 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 84 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 |
wildcardValidPkt.setAddress(addr); | ||
wildcardValidPkt.setPort(socket.getLocalPort()); | ||
*/ | ||
wildcardValidPkt.setAddress(wildcardAddr); |
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.
again enabling setup but not enabling a corrsponding test scenario?
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.
Yes, I thought it cleaner to just disable the test in one place.
/integrate |
Going to push as commit 298dda4.
Your commit was automatically rebased without conflicts. |
@Michael-Mc-Mahon Pushed as commit 298dda4. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi,
JDK-8236852 was fixed in 15 and included its own regression test, but a couple of existing tests have code commented out that also test this functionality. One scenario relating to sending to the wildcard address was not addressed and remains commented out.
Thanks,
Michael.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/14952/head:pull/14952
$ git checkout pull/14952
Update a local copy of the PR:
$ git checkout pull/14952
$ git pull https://git.openjdk.org/jdk.git pull/14952/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 14952
View PR using the GUI difftool:
$ git pr show -t 14952
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/14952.diff
Webrev
Link to Webrev Comment