[android] Android.Device_Emulator.JIT.Test failing on emulators with CoreCLR

[ivanpovazan]

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=953058
Build error leg or test failing: Android.Device_Emulator.JIT.Test
Found in: #112547

Error log

[21:40:21] dbug: ADBRunner using ADB.exe supplied from /datadisks/disk1/work/C3800A6B/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25103.1/tools/net8.0/any/../../../runtimes/any/native/adb/linux/adb
[21:40:21] dbug: Full resolved path:'/datadisks/disk1/work/C3800A6B/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25103.1/runtimes/any/native/adb/linux/adb'
[21:40:21] info: Will attempt to find device supporting architectures: 'x86_64'
[21:40:21] dbug: Executing command: '/datadisks/disk1/work/C3800A6B/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25103.1/runtimes/any/native/adb/linux/adb start-server'
[21:40:21] dbug: 
[21:40:21] info: Finding attached devices/emulators...
[21:40:21] dbug: Executing command: '/datadisks/disk1/work/C3800A6B/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25103.1/runtimes/any/native/adb/linux/adb devices -l'
[21:40:21] dbug: Found 1 possible devices
[21:40:21] dbug: Evaluating output line for device serial: emulator-5554          device product:sdk_phone_x86 model:Android_SDK_built_for_x86 device:generic_x86 transport_id:1
[21:40:21] dbug: Executing command: '/datadisks/disk1/work/C3800A6B/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25103.1/runtimes/any/native/adb/linux/adb -s emulator-5554 shell getprop ro.product.cpu.abilist'
[21:40:21] fail: No attached device supports one of required architectures x86_64
[21:40:21] dbug: No suitable devices found
[21:40:21] crit: Failed to find compatible device: x86_64
[21:40:21] dbug: Saving diagnostics data to '/datadisks/disk1/work/C3800A6B/w/B81A09C5/e/diagnostics.json'
XHarness exit code: 81 (DEVICE_NOT_FOUND)
+ exit 81
+ export _commandExitCode=81
+ /usr/bin/python3 -u /datadisks/disk1/work/C3800A6B/w/B81A09C5/u/xharness-event-processor.py
Reporting 1 events from diagnostics file `/datadisks/disk1/work/C3800A6B/w/B81A09C5/e/diagnostics.json`
Analyzing android/test@None (81)
    Encountered DEVICE_NOT_FOUND
    If this occurs repeatedly, please check for architectural mismatch, e.g. sending arm64_v8a APKs to an x86_64 / x86 only queue

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "crit: Failed to find compatible device: x86_64",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=953058
Error message validated: [crit: Failed to find compatible device: x86_64]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 2/17/2025 9:53:47 AM UTC

Report

Build	Definition	Test	Pull Request
1174954	dotnet/runtime	System.Runtime.InteropServices.Tests.WorkItemExecution
1173340	dotnet/runtime	System.Web.HttpUtility.Tests.WorkItemExecution
1171503	dotnet/runtime	System.Diagnostics.Tracing.Tests.WorkItemExecution	#120462
1171489	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#120624
1171357	dotnet/runtime	System.Net.Mail.Functional.Tests.WorkItemExecution	#120635
1170713	dotnet/runtime	System.Xml.Schema.Extensions.Tests.WorkItemExecution
1170651	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#120449
1170520	dotnet/runtime	System.Xml.Linq.Properties.Tests.WorkItemExecution
1169228	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#120303
1168895	dotnet/runtime	System.Runtime.InteropServices.Tests.WorkItemExecution	#120542
1168872	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#120449
1167112	dotnet/runtime	System.Xml.XmlSerializer.ReflectionOnly.Tests.WorkItemExecution
1166928	dotnet/runtime	System.Xml.Linq.SDMSample.Tests.WorkItemExecution
1166594	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#110472
1165923	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#120351
1165469	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution
1165443	dotnet/runtime	System.Xml.XmlSerializer.ReflectionOnly.Tests.WorkItemExecution
1165042	dotnet/runtime	System.Xml.XmlSerializer.ReflectionOnly.Tests.WorkItemExecution
1164090	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#120313
1163722	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#120326
1163636	dotnet/runtime	System.Xml.Linq.xNodeBuilder.Tests.WorkItemExecution
1162954	dotnet/runtime	System.Runtime.ReflectionInvokeInterpreted.Tests.WorkItemExecution
1161897	dotnet/runtime	System.Xml.Linq.Events.Tests.WorkItemExecution
1160519	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#119758
1159914	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#119684
1159547	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#120158
1158631	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#120124
1158595	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#120098
1158146	dotnet/runtime	System.Xml.Linq.xNodeReader.Tests.WorkItemExecution
1157960	dotnet/runtime	System.Runtime.InteropServices.Tests.WorkItemExecution	#120093
1156728	dotnet/runtime	System.Xml.Linq.xNodeReader.Tests.WorkItemExecution
1156070	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#119998
1155187	dotnet/runtime	System.Diagnostics.Tracing.Tests.WorkItemExecution	#119915
1155145	dotnet/runtime	System.Runtime.InteropServices.Tests.WorkItemExecution	#119963
1154690	dotnet/runtime	System.Xml.Schema.Extensions.Tests.WorkItemExecution
1153985	dotnet/runtime	System.Xml.Linq.xNodeReader.Tests.WorkItemExecution
1153693	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#117168
1153205	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#119898
1153031	dotnet/runtime	System.Runtime.InteropServices.Tests.WorkItemExecution	#119893
1153029	dotnet/runtime	System.Xml.Linq.TreeManipulation.Tests.WorkItemExecution
1152778	dotnet/runtime	System.Xml.Linq.Properties.Tests.WorkItemExecution
1152674	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#119878
1151980	dotnet/runtime	Android.Device_Emulator.NativeAOT.Test.WorkItemExecution
1151516	dotnet/runtime	Android.Device_Emulator.JIT.Static.Test.WorkItemExecution	#119764
1151361	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#119827
1150139	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#119670
1148921	dotnet/runtime	System.Xml.Linq.Events.Tests.WorkItemExecution
1148726	dotnet/runtime	System.Xml.Linq.SDMSample.Tests.WorkItemExecution

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
1	11	48

[ivanpovazan]

@kotlarmilos there is a failure on #112547 indicating that for CoreCLR on Android we use a queue which has only x86 emulators, causing the test to fail as we target x64 specifically.

Do we have queues with x64 emulators only that we could use?

[kotlarmilos]

I am not aware of a separate queue with x64-only emulators. This failure appears to be machine-specific. In successful runs, there are two emulators available, and one is selected. I assume one is x64 and the other is x86. Here is an example of a successful run: https://helixr1107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-112625-merge-5c5e4bed3d564f6eb6/Android.Device_Emulator.JIT.Test.Attempt.2/1/console.7eba4a2f.log?helixlogtype=result

Alternatively, we could restart this specific machine.

/cc: @matouskozak

[matouskozak]

I am not aware of a separate queue with x64-only emulators. This failure appears to be machine-specific. In successful runs, there are two emulators available, and one is selected. I assume one is x64 and the other is x86. Here is an example of a successful run: https://helixr1107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-112625-merge-5c5e4bed3d564f6eb6/Android.Device_Emulator.JIT.Test.Attempt.2/1/console.7eba4a2f.log?helixlogtype=result

I think queues with Android API <= 29 have both x64 and x86 simulators installed and it appears that XHarness is trying to connect to both even though we need just the x64 version. I think re-run would make the test pass.

Alternatively, we could restart this specific machine.

I think these are VMs but you can try asking in First Responders as it seems that this specific VM is on the top of the failures list (in the past 3 days).

[ivanpovazan]

I think queues with Android API <= 29 have both x64 and x86 simulators installed

Yes, I think that is the problem, or better to say that on this particular failure there aren't two emulators installed:

[21:40:21] dbug: Found 1 possible devices
[21:40:21] dbug: Evaluating output line for device serial: emulator-5554          device product:sdk_phone_x86 model:Android_SDK_built_for_x86 device:generic_x86 transport_id:1
[21:40:21] dbug: Executing command: '/datadisks/disk1/work/C3800A6B/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25103.1/runtimes/any/native/adb/linux/adb -s emulator-5554 shell getprop ro.product.cpu.abilist'
[21:40:21] fail: No attached device supports one of required architectures x86_64

Via xharness we:

• first fetch available devices via:
  adb devices -l
• Then for each of them we check the supported architectures:
  adb -s <device-name> shell getprop ro.product.cpu.abilist
• If we find the match, we pick that emulator.
• If we don't find the match, we throw:
  https://github.com/dotnet/xharness/blob/32f83a8881e5142504a9089bac4aa98382a08f75/src/Microsoft.DotNet.XHarness.Android/AdbRunner.cs#L769

I think this host machine just does not have a x64 emulator installed and that is why it fails. The question is, if it is the only host with this problem.

[steveisok]

@ivanpovazan did anyone raise this with FR? They should be able to go into the machines and determine if it's all installed properly.

[ivanpovazan]

I updated the ErrorMessage pattern to: fail: No attached device supports one of required architectures x86_64 as the previous one was picking up cases when there are no devices at all.

[ivanpovazan]

The problematic machines have been deleted. I suggest monitoring this issue for some time, to see if we catch some other misbehaviors.