-
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][MT] WasmBrowserTestRunner.RunConsoleMessagesPump - abrupt disconect #101618
Comments
Tagging subscribers to this area: @dotnet/ncl |
This is complaint by the xharness which is hosting the web server. I think we should just silence the xharness
|
No failures after the fix: dotnet/xharness#1231. |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=657270
Build error leg or test failing: WasmTestOnChrome-MT-System.Net.Http.Functional.Tests.WorkItemExecution
Pull request: #101188
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=657270
Error message validated:
[The remote party closed the WebSocket connection without completing the close handshake
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 4/26/2024 6:13:23 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: