-
Notifications
You must be signed in to change notification settings - Fork 5k
retire DummyTcpServer from SslStream tests #65876
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
Conversation
Tagging subscribers to this area: @dotnet/ncl, @vcsjones Issue Detailscontributes to #52362. When Disposing the server only stops the listener. So we can still have tests running after the test is finished. Related to that (and even more problematic) is fact that we don't have visibility to server failures. So when something fails we get
that is really hard to troubleshoot for random CI failures.
|
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.
Generally looks good, I have 2 comments.
contributes to #52362.
Aside from DummyTcpServer using APM & IAsyncResult that are pain to debug there some other issue:
When Disposing the server only stops the listener. So we can still have tests running after the test is finished. Related to that (and even more problematic) is fact that we don't have visibility to server failures. So when something fails we get
that is really hard to troubleshoot for random CI failures.
Since we already have helper function to get connected stream I switched to that and we await for the server parts as well to have better visibility to failures.