-
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][outerloop] Standup OuterLoop ClientWebSocket tests #45470
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsGet the websocket outerloop tests stood up to run. Ongoing outstanding failures being looked at.
|
- Removes the necessity of setting up a new test. - May want to go back to ActiveIssue for tracking purposes.
/azp run runtime-libraries-mono outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
- Removes the necessity of setting up a new test. - May want to go back to ActiveIssue for tracking purposes.
/azp run outerloop |
No pipelines are associated with this pull request. |
/azp run runtime-libraries-mono outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
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 good
src/libraries/System.Net.WebSockets.Client/tests/ClientWebSocketOptionsTests.cs
Outdated
Show resolved
Hide resolved
…etOptionsTests.cs Point to WebProxy support issue
/azp run runtime-libraries-mono outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @lewing! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
Get the websocket outerloop tests stood up to run.
Ongoing outstanding failures being looked at.
Some tests waiting on #44722 which have been tested against the mods and now pass with them.New issue for CloseOutputAsync: #45468
multiple failures for:The above appears to be an inconsistent response fromWebSockets
and what is returned/expected by managed client. Issue #45538Instead of tracking with ActiveIssue moved the platform detection code and initialization into the test.New issue for Close Description length: #45531 fixed here: #45536
Looking at subprotocol support specified by URI Query: See issue #45583
subprotocols are supported via websockets options and specifying the subprotocol via the AddSubProtocol method.
Intermittent Uncaught RuntimeError: memory access out of bounds: Issue #45586
New issue for AbortTests with varied failure reasons: #45674 Fixed here: #45827
Part of #44666