[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
1322010	dotnet/runtime	Android.Device_Emulator.JIT.Static.Test.WorkItemExecution	#125214
1321993	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#125211
1320367	dotnet/runtime	System.Diagnostics.DiagnosticSource.Tests.WorkItemExecution	#124558
1319961	dotnet/runtime	Android.Device_Emulator.JIT.Static.Test.WorkItemExecution	#125146
1319072	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124977
1319209	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#125080
1319215	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#124930
1316910	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124244
1319057	dotnet/runtime	System.Diagnostics.Tracing.Tests.WorkItemExecution	#125091
1319067	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#125092
1319139	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#125156
1319108	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#125090
1316662	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124804
1319024	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#125152
1318988	dotnet/runtime	System.Runtime.InteropServices.Tests.WorkItemExecution	#125056
1318932	dotnet/runtime	System.Runtime.InteropServices.Tests.WorkItemExecution	#124561
1318535	dotnet/runtime	System.Runtime.InteropServices.Tests.WorkItemExecution	#124994
1318532	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#125139
1318548	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#125088
1318900	dotnet/runtime	System.Net.Mail.Functional.Tests.WorkItemExecution	#125129
1318441	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#125138
1318341	dotnet/runtime	System.Diagnostics.DiagnosticSource.Tests.WorkItemExecution	#125125
1318778	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#125093
1318486	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#125142
1318736	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#125074
1318322	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124701
1318285	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#123323
1318434	dotnet/runtime	System.Net.Mail.Functional.Tests.WorkItemExecution	#123445
1318448	dotnet/runtime	System.Diagnostics.DiagnosticSource.Tests.WorkItemExecution	#125141
1318408	dotnet/runtime	System.Xml.Linq.Properties.Tests.WorkItemExecution
1318108	dotnet/runtime	System.Runtime.InteropServices.Tests.WorkItemExecution	#125093
1318133	dotnet/runtime	Android.Device_Emulator.JIT.Test.WorkItemExecution	#125122
1318148	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124918
1318209	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#125084
1318117	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#125126
1318122	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#125009
1318096	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#124375
1318058	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#124959
1317778	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#124904
1318038	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#125120
1317888	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#125114
1317956	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#124559
1317400	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution
1317133	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#125056
1317158	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#125091
1317144	dotnet/runtime	System.Net.Mail.Functional.Tests.WorkItemExecution	#124842
1317108	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124943
1317083	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#125089
1315476	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124794
1317007	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#125084
1317011	dotnet/runtime	Android.Device_Emulator.JIT.Test.WorkItemExecution	#125072
1316222	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124601
1316244	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#125059
1314593	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124943
1314416	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124997
1314097	dotnet/runtime	System.Net.Mail.Functional.Tests.WorkItemExecution	#124997
1313860	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124990
1313795	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124991
1313773	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124938
1313778	dotnet/runtime	System.Net.Mail.Functional.Tests.WorkItemExecution	#124985
1313319	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124854
1313639	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124830
1313610	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124987
1313537	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124977
1313510	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124919
1313515	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124984
1312850	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124962
1312589	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#123251
1311672	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124920
1311366	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124863
1310998	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#123145
1309930	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#124842
1309874	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#123819
1308167	dotnet/runtime	System.Diagnostics.Tracing.Tests.WorkItemExecution	#124810
1307694	dotnet/runtime	System.Diagnostics.DiagnosticSource.Tests.WorkItemExecution	#124516
1307684	dotnet/runtime	System.Runtime.InteropServices.Tests.WorkItemExecution	#124794
1307597	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124796
1307360	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124789
1307035	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124586
1307000	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124738
1306872	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#124203
1306756	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#124685
1306478	dotnet/runtime	System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandlerTest.LargeUriAndHeaders_Works	#124682
1306526	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124663
1306483	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#124770
1306472	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#123830
1306421	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#124244
1305866	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124590
1305541	dotnet/runtime	System.Net.Mail.Functional.Tests.WorkItemExecution	#124638
1305524	dotnet/runtime	System.Runtime.InteropServices.Tests.WorkItemExecution	#124753
1305436	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124641
1305133	dotnet/runtime	System.Net.WebSockets.Client.Tests.WorkItemExecution	#124699
1305049	dotnet/runtime	System.Net.Mail.Functional.Tests.WorkItemExecution	#123614
1305040	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#124164
1305030	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#124452
1304153	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#124710
1302844	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#124644
1302819	dotnet/runtime	System.Net.Http.Functional.Tests.SocketsHttpHandler_HttpClientHandlerTest.LargeUriAndHeaders_Works	#124660
1302784	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#124655
1302778	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution	#111514
Displaying 100 of 132 results

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
2	69	123

[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.