-
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
[browser][tests] Standup System.Net.WebSockets.Client.Tests in CI #44781
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue Details
|
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.
Looks ok after the loopback activeissue change
- mark the loopback issues as activeIssue - [ActiveIssue("#34690", TestPlatforms.Browser)]
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.
Other than the existing comments, LGTM.
Thanks for the catch Larry : Make browser specific failure browser specific |
Part of #44666
Outstanding for now are the tests that use LoopBack which depends on websockets and are not supported on browser. Marked the loopback issues as activeIssue -
[ActiveIssue("#34690", TestPlatforms.Browser)]
Also, one marked
[ActiveIssue("https://github.com/dotnet/runtime/issues/44720")]
which is being looked into. #44720