-
Notifications
You must be signed in to change notification settings - Fork 4.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
LocalEndPointTestIPv6Sync.TcpAcceptSocket_WhenServerBoundToSpecificAddress_LocalEPIsSame failing #52141
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsRunfo Creating Tracking Issue (data being generated)
|
Call stack:
Failures (3/12-7/22, incl. PRs):
Alternative / related callstack:
Failures (3/12-6/23, incl. PRs):
|
A possible explanation might be that this is yet another dual stack IPv4/IPv6 port-collision issue, caused by other test cases running in parallel. runtime/src/libraries/System.Net.Sockets/tests/FunctionalTests/LocalEndPointTest.cs Lines 152 to 165 in 01b7e73
A dual-mode client in that other test that is intended to connect to it's matching IPv4-only listener may then connect to the We can move the sync tests classes to a non-parallel collection as a quick fix attempt. |
Tagging subscribers to this area: @dotnet/ncl Issue DetailsRunfo Tracking Issue: LocalEndPointTestIPv6Sync.TcpAcceptSocket_WhenServerBoundToSpecificAddress_LocalEPIsSame failing
Build Result Summary
|
Runfo Tracking Issue: LocalEndPointTestIPv6Sync.TcpAcceptSocket_WhenServerBoundToSpecificAddress_LocalEPIsSame failing
Build Result Summary
The text was updated successfully, but these errors were encountered: