Skip to content
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] XHarness SocketException: Transport endpoint is not connected #105370

Closed
carlossanlop opened this issue Jul 23, 2024 · 2 comments
Closed
Assignees
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono Known Build Error Use this to report build issues in the .NET Helix tab os-windows
Milestone

Comments

@carlossanlop
Copy link
Member

carlossanlop commented Jul 23, 2024

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=752655
Build error leg or test failing: browser-wasm windows Release LibraryTests_Smoke_AOT

Error Message

{
  "ErrorMessage" : "Transport endpoint is not connected",
  "BuildRetry" : false,
  "ExcludeConsoleLog" : false
}
console.error: (new AbortError("IndexedDB: main/search-config-overrides-v2 getLastModified() IndexedDB:  execute() A request was aborted, for example through a call to IDBTransaction.abort.", "resource://services-settings/IDBHelpers.sys.mjs", 16))
[22:45:33] crit: System.Net.Sockets.SocketException (107): Transport endpoint is not connected
                    at System.Net.Sockets.Socket.get_RemoteEndPoint()
                    at System.Net.Http.HttpConnectionPool.<ConnectAsync>g__GetRemoteEndPoint|51_0(Stream stream)
                    at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
                    at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
                    at System.Net.Http.HttpConnectionPool.InjectNewHttp11ConnectionAsync(QueueItem queueItem)
                    at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
                    at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
                    at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
                    at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
                    at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
                    at OpenQA.Selenium.Remote.HttpCommandExecutor.MakeHttpRequest(HttpRequestInfo requestInfo)
                    at OpenQA.Selenium.Remote.HttpCommandExecutor.Execute(Command commandToExecute)
                    at OpenQA.Selenium.Remote.DriverServiceCommandExecutor.Execute(Command commandToExecute)
                    at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
                    at OpenQA.Selenium.Remote.RemoteWebDriver.Dispose(Boolean disposing)
                    at OpenQA.Selenium.Remote.RemoteWebDriver.Dispose()
                    at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmTestBrowserCommand.InvokeInternal(ILogger logger) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/WASM/Browser/WasmTestBrowserCommand.cs:line 108
                    at Microsoft.DotNet.XHarness.CLI.Commands.Wasm.WasmTestBrowserCommand.InvokeInternal(ILogger logger)
                    at Microsoft.DotNet.XHarness.CLI.Commands.XHarnessCommand`1.Invoke(IEnumerable`1 arguments) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/XHarnessCommand.cs:line 145
XHarness exit code: 71 (GENERAL_FAILURE)

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=752655
Error message validated: [Transport endpoint is not connected]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/23/2024 11:49:11 PM UTC

Report

Build Definition Test Pull Request
768664 dotnet/runtime WasmTestOnFirefox-ST-Microsoft.CSharp.Tests.WorkItemExecution #106078
767493 dotnet/runtime WasmTestOnFirefox-MT-System.Threading.Timer.Tests.WorkItemExecution #106030
766322 dotnet/runtime WasmTestOnFirefox-MT-System.Xml.Linq.Axes.Tests.WorkItemExecution #105879
764961 dotnet/runtime WasmTestOnFirefox-ST-System.IO.Packaging.Tests.WorkItemExecution #105910
763061 dotnet/runtime WasmTestOnFirefox-ST-System.Threading.Overlapped.Tests.WorkItemExecution #105548
761368 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.Serialization.Xml.ReflectionOnly.Tests.WorkItemExecution #105464
755184 dotnet/runtime WasmTestOnFirefox-ST-System.IO.Packaging.Tests.WorkItemExecution #103861
753448 dotnet/runtime WasmTestOnFirefox-MT-System.Runtime.Extensions.Tests.WorkItemExecution #105027
752655 dotnet/runtime WasmTestOnFirefox-ST-System.Xml.Linq.Events.Tests.WorkItemExecution #105352

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 9
@carlossanlop carlossanlop added arch-wasm WebAssembly architecture os-windows area-VM-meta-mono Known Build Error Use this to report build issues in the .NET Helix tab labels Jul 23, 2024
Copy link
Contributor

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Jul 23, 2024
@maraf
Copy link
Member

maraf commented Jul 29, 2024

Looks like some firefox specific thing. No idea, maybe something like maintance? Does firefox driver have some configuration that we could set?
(Looking for the addons seems unoptimal as well).

@maraf maraf added this to the 10.0.0 milestone Jul 29, 2024
@maraf maraf removed the untriaged New issue has not been triaged by the area owner label Jul 29, 2024
@pavelsavara pavelsavara modified the milestones: 10.0.0, 9.0.0 Jul 29, 2024
@lewing lewing modified the milestones: 9.0.0, 10.0.0 Aug 14, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Sep 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono Known Build Error Use this to report build issues in the .NET Helix tab os-windows
Projects
None yet
Development

No branches or pull requests

4 participants