-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[wasm] Enable System.Net.WebSockets.Tests.WebSocketTests class #38807
Labels
Milestone
Comments
Dotnet-GitSync-Bot
added
area-System.Net
untriaged
New issue has not been triaged by the area owner
labels
Jul 6, 2020
Tagging subscribers to this area: @dotnet/ncl |
MaximLipnin
changed the title
[wasm] Enable System.Net.WebSockets.Tests
[wasm] Enable System.Net.WebSockets.Tests.WebSocketTests class
Jul 6, 2020
This was referenced Jul 6, 2020
Jacksondr5
pushed a commit
to Jacksondr5/runtime
that referenced
this issue
Aug 10, 2020
…ace (dotnet#40004) There is no repro for dotnet#38807 at the moment so the related tests have been enabled. Two tests have been disabled due to PNSE (see dotnet#39346). Fixes: dotnet#38807 The test run result: `Tests run: 177, Errors: 0, Failures: 0, Skipped: 0.`
ghost
locked as resolved and limited conversation to collaborators
Dec 8, 2020
carlossanlop
pushed a commit
to carlossanlop/maintenance-packages
that referenced
this issue
Jan 26, 2024
…ace (#40004) There is no repro for dotnet/runtime#38807 at the moment so the related tests have been enabled. Two tests have been disabled due to PNSE (see dotnet/runtime#39346). Fixes: dotnet/runtime#38807 The test run result: `Tests run: 177, Errors: 0, Failures: 0, Skipped: 0.`
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the moment
System.Net.WebSockets.Tests
crashes with:@vargaz made some fix for that emscripten-core/emscripten#11482. Among others, it should be included to the emscripten release version which we could bump in dotnet/runtime. So the respective tests could be enabled.
The text was updated successfully, but these errors were encountered: