-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Socket.Tests: remove TestSettings.UDPRedundancy #44202
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
Socket.Tests: remove TestSettings.UDPRedundancy #44202
Conversation
|
Tagging subscribers to this area: @dotnet/ncl |
|
/cc @wfurt |
stephentoub
left a 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.
LGTM if @wfurt is happy with it (he's been looking a lot at test failures).
|
I think this may be ok - I certainly like the simplification. We can watch the results and react if we see new failures. |
wfurt
left a 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.
LGTM
|
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
The The |
|
/azp run runtime-libraries-coreclr outerloop |
|
/azp run runtime |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
dotnet/corefx#15697 changed this value to 1, and no-one touched it since then.
As the comment in that PR points out, the root cause of the UDP test failures wasn't packet loss, but IPv4 / IPv6 port collision on Unix in dual-mode cases.
The value and the for loops are complicating Socket test code unnecessarily, simplification seems reasonable.
/cc @geoffkizer @stephentoub