-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[QUIC] Fix TestConnect #49660
[QUIC] Fix TestConnect #49660
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsContributes to #49157
|
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.
Just a question about the ActiveIssue
, otherwise LGTM, thanks.
@@ -82,6 +82,7 @@ public async Task SetListenerTimeoutWorksWithSmallTimeout() | |||
await Assert.ThrowsAsync<QuicOperationAbortedException>(async () => await serverConnection.AcceptStreamAsync().TimeoutAfter(100000)); | |||
} | |||
|
|||
[ActiveIssue("https://github.com/dotnet/runtime/issues/49157")] |
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.
We're not running these in CI AFAIK so the failures are not blocking any PRs. This will disable them for our local runs, is that what you're goal here is?
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.
Yep, it is for us to have a clean local test run, since we are to start adding new changes. So if some new failures appear, we will know it was because of our changes
Failures are unrelated. |
Contributes to #49157