Skip to content

Conversation

@wfurt
Copy link
Member

@wfurt wfurt commented Aug 4, 2021

I don't think it is safe to use RunClientServer in this case (tried to explain in #56347)
So I updated test not to use it as well as there are no semaphores any more.
Did few hundreds runs over night without sign of problem.
I may update the stream establishment to helper function if we end up using that pattern more.

Fixes #55948

@wfurt wfurt requested a review from a team August 4, 2021 15:20
@wfurt wfurt self-assigned this Aug 4, 2021
@ghost
Copy link

ghost commented Aug 4, 2021

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

Issue Details

I don't think it is safe to use RunClientServer in this case (tried to explain in#56347)
So I updated test not to use it as well as there are no semaphores any more.
Did few hundreds runs over night without sign of problem.
I may update the stream establishment to helper function if we end up using that pattern more.

Fixes #55948

Author: wfurt
Assignees: wfurt
Labels:

area-System.Net.Quic

Milestone: -

@wfurt wfurt merged commit 42066d6 into dotnet:main Aug 5, 2021
@wfurt wfurt deleted the ReadAborted_55948 branch August 5, 2021 00:26
@karelz karelz added this to the 6.0.0 milestone Aug 17, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Sep 16, 2021
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.

[QUIC] test timing out System.Net.Quic.Tests.QuicStreamTests_MsQuicProvider.ReadOutstanding_ReadAborted_Throws

3 participants