Repository navigation
Failed USB connection via port 54050, error 61, in tvOS arm64 Release AllSubsets_Mono #82637
Description
- Affected PR: [7.0] Fix intellisense xml file selection from 'net' or 'dotnet-plat-ext' #82554
- Affected queue:
Build tvOS arm64 Release AllSubsets_Mono - Job result: https://dev.azure.com/dnceng-public/public/public%20Team/_build/results?buildId=182544&view=logs&j=f4520fb1-1559-5885-1d9c-3cb3f6a85e23&t=6c7a8cfe-f92e-569a-eef9-b2ad3e13056d&l=57
- Artifacts: https://dev.azure.com/dnceng-public/public/_build/results?buildId=182544&view=ms.vss-test-web.build-test-results-tab&runId=3552693&resultId=100001&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab
- console.log output file repeatedly shows the USB connection error below: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-82554-merge-8bea006df9294c8cbf/System.Runtime.Tests/1/console.76e18c2e.log?helixlogtype=result
[13:58:26] dbug: [TCP tunnel] Xamarin.Hosting: Failed to connect to port 54050 (8915) on device (error: 61)
[13:58:26] dbug: [TCP tunnel] Xamarin.Hosting: Attempting USB tunnel between the port 54050 on the device and the port 54050 (8915) on the mac: 61
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.
Edit. Removed the match string because the error message was matching un-related failures.
{
"ErrorMessage": "",
"BuildRetry": false,
"ErrorPattern": "",
"ExcludeConsoleLog": false
}Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 0 |
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=323893
Error message validated: Xamarin.Hosting: Failed to connect to port
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/28/2023 9:28:49 PM UTC
Activity
lewing commentedon Feb 24, 2023
dotnet/arcade#11683
steveisok commentedon Feb 24, 2023
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.
carlossanlop commentedon May 30, 2023
I originally logged this issue for tvOS, but I'm also seeing it in iOS arm64. Here is a fresh example:
ios-arm64 Release AllSubsets_Monokotlarmilos commentedon Jun 30, 2023
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?
/cc @akoeplinger @steveisok
premun commentedon Jun 30, 2023
@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?
kotlarmilos commentedon Jun 30, 2023
Host: osx-arm64
Device: iPhone iOS 16.5.1
Xcode: 14.3.1 (14E300c)
Download the bundle and place it in a test directory.
tracing_eventpipe_tcp_issue.zip
Run the following script from the local directory:
The test should start executing and may fail (due to other reasons), but the TCP connection is not established. The app fails locally with
5 remaining items
ivanpovazan commentedon Jun 25, 2024
@kotlarmilos and myself are looking into this.
matouskozak commentedon Aug 5, 2024
Removing the
Xamarin.Hosting: Failed to connect to portmatch string because it's too general and it's matching un-related failures. I'll keep the issue fyi: @ivanpovazan @kotlarmilosjeffschwMSFT commentedon Sep 11, 2024
removing 'blocking-clean-ci' as it has not failed in 30 days
kotlarmilos commentedon Jun 18, 2025
Switched to file copy in dotnet/xharness#1416.