Mono Bionic arm64 CI failure: No attached devices found

[carlossanlop]

Found in this release/7.0 backport PR: #76052

Please help determine if a backport fix is needed.

• Queue: Build Linux_bionic arm64 Release AllSubsets_Mono
• Job results: https://dev.azure.com/dnceng-public/public/public%20Team/_build/results?buildId=29620&view=logs&j=30e4a6b3-73be-5b96-c535-0d9023575f9c&t=80b5ca1e-012b-5240-15a1-0677df5434af&l=58
• Test: Microsoft.Extensions.Options
• Log file: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-76052-merge-e753eaafe08545388c/Microsoft.Extensions.Options.Tests/1/console.04bdeeab.log?helixlogtype=result

Callstack

[18:18:27] info: Required architecture: 'arm64-v8a'
[18:18:27] dbug: ADBRunner using ADB.exe supplied from C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\tools\net7.0\any\..\..\..\runtimes\any\native\adb\windows\adb.exe
[18:18:27] dbug: Full resolved path:'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe'
[18:18:27] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe start-server'
[18:18:29] dbug: 
[18:18:29] info: Finding attached devices/emulators...
[18:18:29] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:18:29] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:18:29] dbug: Attempt 1 failed, retrying in 10 seconds...
[18:18:39] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:18:39] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:18:39] dbug: Attempt 2 failed, retrying in 10 seconds...
[18:18:49] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:18:49] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:18:49] dbug: Attempt 3 failed, retrying in 10 seconds...
[18:18:59] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:00] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:00] dbug: Attempt 4 failed, retrying in 10 seconds...
[18:19:10] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:10] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:10] dbug: Attempt 5 failed, retrying in 10 seconds...
[18:19:20] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:20] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:20] dbug: Attempt 6 failed, retrying in 10 seconds...
[18:19:30] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:30] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:30] dbug: Attempt 7 failed, retrying in 10 seconds...
[18:19:40] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:40] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:40] dbug: Attempt 8 failed, retrying in 10 seconds...
[18:19:50] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:50] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:50] dbug: Attempt 9 failed, retrying in 10 seconds...
[18:20:00] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:20:00] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:20:00] dbug: All 9 retries of action failed
[18:20:00] warn: No attached devices / emulators detected. Check that any emulators have been started, and attached device(s) are connected via USB, powered-on, unlocked and authorized.
[18:20:00] dbug: No suitable devices found
[18:20:00] crit: Failed to find compatible device: arm64-v8a

[ghost]

Tagging subscribers to this area: @dotnet/area-extensions-options
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Found in this release/7.0 backport PR: #76052

Please help determine if a backport fix is needed.

• Queue: Build Linux_bionic arm64 Release AllSubsets_Mono
• Job results: https://dev.azure.com/dnceng-public/public/public%20Team/_build/results?buildId=29620&view=logs&j=30e4a6b3-73be-5b96-c535-0d9023575f9c&t=80b5ca1e-012b-5240-15a1-0677df5434af&l=58
• Test: Microsoft.Extensions.Options
• Log file: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-76052-merge-e753eaafe08545388c/Microsoft.Extensions.Options.Tests/1/console.04bdeeab.log?helixlogtype=result

Callstack

[18:18:27] info: Required architecture: 'arm64-v8a'
[18:18:27] dbug: ADBRunner using ADB.exe supplied from C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\tools\net7.0\any\..\..\..\runtimes\any\native\adb\windows\adb.exe
[18:18:27] dbug: Full resolved path:'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe'
[18:18:27] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe start-server'
[18:18:29] dbug: 
[18:18:29] info: Finding attached devices/emulators...
[18:18:29] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:18:29] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:18:29] dbug: Attempt 1 failed, retrying in 10 seconds...
[18:18:39] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:18:39] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:18:39] dbug: Attempt 2 failed, retrying in 10 seconds...
[18:18:49] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:18:49] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:18:49] dbug: Attempt 3 failed, retrying in 10 seconds...
[18:18:59] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:00] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:00] dbug: Attempt 4 failed, retrying in 10 seconds...
[18:19:10] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:10] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:10] dbug: Attempt 5 failed, retrying in 10 seconds...
[18:19:20] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:20] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:20] dbug: Attempt 6 failed, retrying in 10 seconds...
[18:19:30] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:30] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:30] dbug: Attempt 7 failed, retrying in 10 seconds...
[18:19:40] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:40] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:40] dbug: Attempt 8 failed, retrying in 10 seconds...
[18:19:50] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:50] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:50] dbug: Attempt 9 failed, retrying in 10 seconds...
[18:20:00] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:20:00] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:20:00] dbug: All 9 retries of action failed
[18:20:00] warn: No attached devices / emulators detected. Check that any emulators have been started, and attached device(s) are connected via USB, powered-on, unlocked and authorized.
[18:20:00] dbug: No suitable devices found
[18:20:00] crit: Failed to find compatible device: arm64-v8a

Author:	carlossanlop
Assignees:	-
Labels:	arch-arm64, os-linux, area-VM-meta-mono, area-Extensions-Options, test-failure
Milestone:	-

[ghost]

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Found in this release/7.0 backport PR: #76052

Please help determine if a backport fix is needed.

• Queue: Build Linux_bionic arm64 Release AllSubsets_Mono
• Job results: https://dev.azure.com/dnceng-public/public/public%20Team/_build/results?buildId=29620&view=logs&j=30e4a6b3-73be-5b96-c535-0d9023575f9c&t=80b5ca1e-012b-5240-15a1-0677df5434af&l=58
• Test: Microsoft.Extensions.Options
• Log file: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-76052-merge-e753eaafe08545388c/Microsoft.Extensions.Options.Tests/1/console.04bdeeab.log?helixlogtype=result

Callstack

[18:18:27] info: Required architecture: 'arm64-v8a'
[18:18:27] dbug: ADBRunner using ADB.exe supplied from C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\tools\net7.0\any\..\..\..\runtimes\any\native\adb\windows\adb.exe
[18:18:27] dbug: Full resolved path:'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe'
[18:18:27] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe start-server'
[18:18:29] dbug: 
[18:18:29] info: Finding attached devices/emulators...
[18:18:29] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:18:29] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:18:29] dbug: Attempt 1 failed, retrying in 10 seconds...
[18:18:39] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:18:39] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:18:39] dbug: Attempt 2 failed, retrying in 10 seconds...
[18:18:49] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:18:49] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:18:49] dbug: Attempt 3 failed, retrying in 10 seconds...
[18:18:59] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:00] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:00] dbug: Attempt 4 failed, retrying in 10 seconds...
[18:19:10] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:10] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:10] dbug: Attempt 5 failed, retrying in 10 seconds...
[18:19:20] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:20] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:20] dbug: Attempt 6 failed, retrying in 10 seconds...
[18:19:30] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:30] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:30] dbug: Attempt 7 failed, retrying in 10 seconds...
[18:19:40] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:40] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:40] dbug: Attempt 8 failed, retrying in 10 seconds...
[18:19:50] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:19:50] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:19:50] dbug: Attempt 9 failed, retrying in 10 seconds...
[18:20:00] dbug: Executing command: 'C:\h\w\B35A09A7\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22411.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[18:20:00] dbug: No attached devices found
                 Exit code: 0
                 Std out:
                 List of devices attached
                 
                 
                 
                 
[18:20:00] dbug: All 9 retries of action failed
[18:20:00] warn: No attached devices / emulators detected. Check that any emulators have been started, and attached device(s) are connected via USB, powered-on, unlocked and authorized.
[18:20:00] dbug: No suitable devices found
[18:20:00] crit: Failed to find compatible device: arm64-v8a

Author:	carlossanlop
Assignees:	-
Labels:	arch-arm64, os-linux, untriaged, area-Infrastructure-mono, area-VM-meta-mono, area-Extensions-Options, test-failure
Milestone:	-

[steveisok]

@akoeplinger this still happens from time to time. Is there anything we can really do about it?