-
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-mt] WasmTestOnBrowser-System.Net.WebSockets.Client.Tests fails #74413
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsThere are 123 failing tests in
|
Tagging subscribers to this area: @dotnet/ncl Issue DetailsThere are 123 failing tests in
|
We had a similar |
I am seeing a very similar error message:
Example callstack:
|
That's kind of unexpected, we shouldn't be using a shared array buffer on single-threaded wasm. @lewing I think we may need a separate issue |
This log is MT build. |
There are 123 failing tests in
WasmTestOnBrowser-System.Net.WebSockets.Client.Tests
when multi-threading is enabled.Full console log: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-74342-merge-b05c5a1bd5ab47119e/WasmTestOnBrowser-System.Net.WebSockets.Client.Tests/1/console.c02a8019.log?helixlogtype=result
The text was updated successfully, but these errors were encountered: