-
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] Failure in System.Net.WebSockets.Client.Tests.SendReceiveTest.SendReceive_Concurrent_Success #57519
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue Details#57464 Has a failure that looks worth investigating.
|
@pavelsavara is this similar to the failure you saw? |
This is same as #53957, but happened in different test. |
Possibly related failure I was able to reproduce locally.
And also
And also
|
The same failure happened again in #57742
and another one posted by @pavelsavara above
@lewing is all of it now tracked by #53957 or should we reopen this one too? |
Let's reopen it. It's different test |
Top post updated with more occurrences. Interestingly the one @CarnaViire hit is not in Kusto ... weird. |
@pavelsavara, what's the status? |
Failures 6/27-8/27 (incl. PRs):
https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-57464-merge-1dac8c21ed9a4cf28a/System.Net.WebSockets.Client.Tests/1/console.df96303b.log?sv=2019-07-07&se=2021-09-05T03%3A12%3A54Z&sr=c&sp=rl&sig=g6Rf5539do7uVURpujLQVt5EWAvjVJ62rSoZmrjIWMs%3D
#57464 Has a failure that looks worth investigating.
The text was updated successfully, but these errors were encountered: