Skip to content
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

Fix Connect_DualMode_DnsConnect_RetrievedEndPoints_Success on Linux #54681

Conversation

antonfirsov
Copy link
Member

@antonfirsov antonfirsov commented Jun 24, 2021

50 failures in ~20 days. See #54677 (comment).

/cc @tmds

Fixes #54677

@ghost
Copy link

ghost commented Jun 24, 2021

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

50 failures in ~20 days. See #54677 (comment).

/cc @tmds

Author: antonfirsov
Assignees: -
Labels:

area-System.Net.Sockets

Milestone: -

@@ -109,6 +109,7 @@ public async Task Connect_DualMode_MultiAddressFamilyConnect_RetrievedEndPoints_
}

[Fact]
[ActiveIssue("https://github.com/dotnet/runtime/issues/54677", TestPlatforms.Linux)]
Copy link
Member

@tmds tmds Jun 24, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@antonfirsov can you update the test so both IPAddress.Loopback.MapToIPv6() and IPAddress.IPv6Loopback are allowed for localEndPoint.Address?

I expect for remoteEndPoint.Address we should stick to IPAddress.Loopback.MapToIPv6() only because the test server is bound to IPAddress.Loopback.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right. I overlooked the exception message, and for some reason thought LocalEndPoint was IPv4, not ::1.
Makes sense to fix the test instead of disabling.

@antonfirsov
Copy link
Member Author

I updated this to fix #54677, instead of disabling, let's wait for CI before merging.

@antonfirsov antonfirsov changed the title Disable Connect_DualMode_DnsConnect_RetrievedEndPoints_Success on Linux Fix Connect_DualMode_DnsConnect_RetrievedEndPoints_Success on Linux Jun 24, 2021
@antonfirsov
Copy link
Member Author

/azp run runtime

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@danmoseley
Copy link
Member

@stephentoub this looks related to your change:

Assert.Throws() Failure
Expected: typeof(System.OperationCanceledException)
Actual:   (No exception was thrown)


Stack trace
   at System.Threading.Tests.PeriodicTimerTests.WaitForNextTickAsync_CanceledWaitThenWaitAgain_Succeeds() in /_/src/libraries/System.Runtime/tests/System/Threading/PeriodicTimerTests.cs:line 186
--- End of stack trace from previous location ---

https://dev.azure.com/dnceng/public/_build/results?buildId=1204988&view=ms.vss-test-web.build-test-results-tab&runId=36060014&resultId=173000&paneView=debug

@stephentoub
Copy link
Member

@danmoseley, that's #54713

@danmoseley
Copy link
Member

@stephentoub thanks, I pasted in the wrong output.

Co-authored-by: Tom Deseyn <tom.deseyn@gmail.com>
Copy link
Member

@tmds tmds left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Connect_DualMode_DnsConnect_RetrievedEndPoints_Success - Assert ::1
5 participants