Skip to content

Conversation

@kjpou1
Copy link
Contributor

@kjpou1 kjpou1 commented Dec 2, 2020

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:

System.Runtime.InteropServices.JavaScript.JSException : InvalidAccessError: Failed to execute 'close' on 'WebSocket': The code must be either 1000, or between 3000 and 4999. 1003 is neither.

The above appears to be an inconsistent response from WebSockets and what is returned/expected by managed client. Issue #45538

Instead 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

  fail: [out of order message from the browser]: http://127.0.0.1:58688/dotnet.js 9661 WebSocket connection to 'ws://corefx-net-http11.azurewebsites.net/WebSocket/EchoWebSocket.ashx?subprotocol=CustomProtocol' failed: Error during WebSocket handshake: Unexpected response code: 400
  fail: [FAIL] System.Net.WebSockets.Client.Tests.ConnectTest.ConnectAsync_PassNoSubProtocol_ServerRequires_ThrowsWebSocketException(server: ws://corefx-net-http11.azurewebsites.net/WebSocket/EchoWebSocket.ashx)
  info: Assert.True() Failure
  info: Expected: True
  info: Actual:   False
  info:    at System.Net.WebSockets.Client.Tests.ConnectTest.ConnectAsync_PassNoSubProtocol_ServerRequires_ThrowsWebSocketException(Uri server)

subprotocols are supported via websockets options and specifying the subprotocol via the AddSubProtocol method.

cws.Options.AddSubProtocol(AcceptedProtocol);

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

@kjpou1 kjpou1 added arch-wasm WebAssembly architecture area-System.Net labels Dec 2, 2020
@kjpou1 kjpou1 self-assigned this Dec 2, 2020
@ghost
Copy link

ghost commented Dec 2, 2020

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

Issue Details

Get the websocket outerloop tests stood up to run.

Ongoing outstanding failures being looked at.

Author: kjpou1
Assignees: kjpou1
Labels:

arch-wasm, area-System.Net

Milestone: -

@akoeplinger
Copy link
Member

/azp run runtime-libraries-mono outerloop

@azure-pipelines
Copy link

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.
@kjpou1 kjpou1 marked this pull request as ready for review December 9, 2020 11:04
@kjpou1
Copy link
Contributor Author

kjpou1 commented Dec 9, 2020

/azp run outerloop

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@kjpou1
Copy link
Contributor Author

kjpou1 commented Dec 9, 2020

/azp run runtime-libraries-mono outerloop

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@lewing lewing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

…etOptionsTests.cs


Point to WebProxy support issue
@lewing
Copy link
Member

lewing commented Dec 11, 2020

/azp run runtime-libraries-mono outerloop

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ghost
Copy link

ghost commented Dec 11, 2020

Hello @lewing!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

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 (@msftbot) and give me an instruction to get started! Learn more here.

@kjpou1 kjpou1 merged commit 8cd2d30 into dotnet:master Dec 11, 2020
@kjpou1 kjpou1 deleted the wasm-websocket-outerloop branch December 11, 2020 04:41
@lewing lewing changed the title [browser][tests][outerloop] Standup OuterLoop WebSocket tests [browser][tests][outerloop] Standup OuterLoop ClientWebSocket tests Dec 11, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jan 10, 2021
@karelz karelz added this to the 6.0.0 milestone Jan 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

arch-wasm WebAssembly architecture area-System.Net

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants