arcade: Failed to find compatible device: arm64-v8a
- 9/13 - 15374 - 1x hit:
- System.ComponentModel.EventBasedAsync.Tests Work Item - DNCENGWIN-116
- 9/13 - 14506 - 1x hit:
- System.CodeDom.Tests Work Item - DNCENGWIN-116
- 9/12 - 13766 - 1x hit:
- System.Net.Http.Json.Unit.Tests Work Item - DNCENGWIN-116
- 9/8 AM Rolling run 8501 - 4x hits:
- System.Net.Http.Functional.Tests Work Item - DNCENGWIN-085
- System.IO.FileSystem.DriveInfo.Tests Work Item - DNCENGWIN-117
- System.ComponentModel.TypeConverter.Tests Work Item - DNCENGWIN-055
- System.ComponentModel.EventBasedAsync.Tests Work Item - DNCENGWIN-097
- 9/7 PM Rolling run 7900 - 2x hits:
- System.DirectoryServices.Protocols.Tests Work Item - DNCENGWIN-097
- System.Composition.Convention.Tests Work Item - DNCENGWIN-117
- 9/7 AM Rolling run 6968 - 2x hits:
- System.Diagnostics.Tracing.Tests Work Item - DNCENGWIN-085
- Microsoft.Extensions.Configuration.Tests Work Item - DNCENGWIN-062
- 9/5 PM Rolling run 5191 - 1x hit:
- System.ComponentModel.EventBasedAsync.Tests Work Item - DNCENGWIN-098
- 9/5 AM Rolling run 4698 - 3x hits:
- Microsoft.Extensions.Configuration.Json.Tests Work Item - DNCENGWIN-071
- Microsoft.Extensions.Primitives.Tests Work Item - DNCENGWIN-098
- System.Linq.Tests Work Item - DNCENGWIN-081
- 9/4 PM Rolling run 4489 - 2x hits:
- System.Net.ServicePoint.Tests Work Item - DNCENGWIN-098
- Microsoft.Extensions.FileSystemGlobbing.Tests Work Item - DNCENGWIN-081
- 9/3 PM Rolling run 4234 - 2x hits:
- System.Numerics.Vectors.Tests - DNCENGWIN-098
- Microsoft.Extensions.Configuration.Json.Tests - DNCENGWIN-081
- 9/2 PM Rolling run 3461 - 1x hit:
- Microsoft.Extensions.DependencyModel.Tests - DNCENGWIN-081
- 9/2 AM Rolling run 2661 - 2x hits:
- System.ComponentModel.TypeConverter - DNCENGWIN-085
- System.ComponentModel.EventBasedAsync - DNCENGWIN-081
- gap in runs 8/27-9/2
- 8/27 PM Rolling run 1972127 - 3x hits:
- System.Net.Security.Tests Work Item - DNCENGWIN-118
- System.Net.Http.Unit.Tests Work Item - DNCENGWIN-048
- System.Linq.Tests Work Item - DNCENGWIN-053
- 8/27 AM Rolling run 1971504 - 3x hits:
- 8/26 PM Rolling run 1970381 - 3x hits:
net7.0-Linux-Release-arm64-Mono_Release_LinuxBionic-Windows.10.Amd64.Android.Open
Example of log:
[14:37:54] dbug: Attempt 9 failed, retrying in 10 seconds...
[14:38:04] dbug: Executing command: 'C:\h\w\AA090904\p\microsoft.dotnet.xharness.cli\1.0.0-prerelease.22422.1\runtimes\any\native\adb\windows\adb.exe devices -l'
[14:38:04] dbug: No attached devices found
Exit code: 0
Std out:
List of devices attached
[14:38:04] dbug: All 9 retries of action failed
[14:38:04] 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.
[14:38:04] dbug: No suitable devices found
[14:38:04] crit: Failed to find compatible device: arm64-v8a
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (18 by maintainers)
@karelz I am looking at your logs more closely, there is probably some regression in dotnet/runtime.
At the very end I can see this:
This means that we cannot collect telemetry + the work item is not retried. I think this will bring your reliability down a lot (plus we won’t get an alert).
Newly failing
097and117were also just disabled and IcM ticket openedYep, looks like this is being handled in #10548. There’s an open ICM. There may need to be some additions to it. @dotnet/dnceng will someone on FR please help with that?
Machines -048, -062 and -118 are clearly misbehaving, I’ve taken them offline for now.
Acknowledged, investigating.