Failed USB connection via port 54050, error 61, in tvOS arm64 Release AllSubsets_Mono #82637
Comments
carlossanlop
added
arch-arm64
blocking-clean-ci
|
Tagging subscribers to 'os-tvos': @steveisok, @akoeplinger Issue Details
It's a bit confusing, since there's a net.dot.System.Runtime.Tests.log output file that shows some succeeded System.Runtime test executions. Anyway, the USB failure seems to be unique, so I'm adding the "known issue" json text to track it. {
"ErrorMessage": "Xamarin.Hosting: Failed to connect to port 54050 (8915) on device (error: 61)",
"BuildRetry": false,
"ErrorPattern": "",
"ExcludeConsoleLog": false
}
|
|
Might be better to keep this open since it's tagged with a known build error label. I don't think we need to have blocking clean ci attached to it. |
steveisok
removed
the
blocking-clean-ci
|
I originally logged this issue for tvOS, but I'm also seeing it in iOS arm64. Here is a fresh example:
|
|
https://helix.dot.net/api/jobs/4cbf9a6d-6389-43f9-9e2c-16540105525e/workitems?api-version=2019-06-17 Both tests pass based on the logs, but one of them is unable to establish a connection via TCP, while the other establishes a connection every time. This failure seems to be permanent and could be a good starting point for identifying the issue. When I attempted to reproduce the error locally, I encountered the same issue. However, I have not opened any ports, which might be a possible cause. I assume that the CI machines have ports 49152-65535 (source https://support.apple.com/en-us/HT202944). I wonder if certain ports are busy or if there might be a firewall misconfiguration. @premun Any ideas why the error persists when running the functional test? |
|
@kotlarmilos if this was firewall misconfiguration, I think we should see the same set of machines failing. I don't think this is the case: https://dataexplorer.azure.com/clusters/engsrvprod/databases/engineeringdata?query=H4sIAAAAAAAAAx3MuwoCMRAF0N6vGLbabQI+ECy2EgsLBSvrMbmQoJmESaKr+PEu9odzTXo/VsSy+NLLQ0GHKdR9cqBxpN2KWBxdGhrOHEFBqO9SmcxybTi67cZwzg/Up0kZ0g3zUlqMrOEDsqlJ7Qe6venE1gf5HzNRiINSDrCetf4ANsm6/4QAAAA= Seems like this is not tied to specific machines?
Do I understand it correctly that you have 100% repro with a specific app? |
|
Host: osx-arm64
# Using bash on Linux/MacOS
curl -L https://aka.ms/get-xharness | bash -
./xharness apple test --app "<LOCAL_DIRECTORY>/tracing_eventpipe_tcp_issue.app" --target "ios-device" --output-directory "<LOCAL_DIRECTORY>/output" --set-env=MONO_APPLE_APP_ENTRY_POINT_LIB_NAME=testdir-buffersize/buffersize.dll --set-env=MONO_APPLE_APP_ASSEMBLY_LOAD_PREFIX=testdir-buffersize --xcode /Applications/Xcode.app -v --launch-timeout 00:05:00The test should start executing and may fail (due to other reasons), but the TCP connection is not established. The app fails locally with |
The runtime test did not utilize the TestRunner, and it was expected to fail. After further investigation and monitoring of the CI, it appears that the TCP failures might be related to the app. If such a failure occurs, ensure that the app functions correctly or consider using |
ericstj
changed the title
|
Removed [7.0] from the title since this appears to be happening across branches. |
|
@ivanpovazan If you try to run the library tests using the |
ghost
added
the
Build tvOS arm64 Release AllSubsets_MonoIt's a bit confusing, since there's a net.dot.System.Runtime.Tests.log output file that shows some succeeded System.Runtime test executions.
Anyway, the USB failure seems to be unique, so I'm adding the "known issue" json text to track it.
{ "ErrorMessage": "Xamarin.Hosting: Failed to connect to port", "BuildRetry": false, "ErrorPattern": "", "ExcludeConsoleLog": false }Report
Summary
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=323893
Error message validated:
Xamarin.Hosting: Failed to connect to portResult validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/28/2023 9:28:49 PM UTC
The text was updated successfully, but these errors were encountered: