Repository navigation
[android] Android.Device_Emulator.JIT.Test failing on emulators with CoreCLR #112633
Description
Activity
@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?
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
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).
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_64Via 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.
- first fetch available devices via:
@ivanpovazan did anyone raise this with FR? They should be able to go into the machines and determine if it's all installed properly.
Reacted by Ivan PovazanI updated the
ErrorMessagepattern to:fail: No attached device supports one of required architectures x86_64as the previous one was picking up cases when there are no devices at all.The problematic machines have been deleted. I suggest monitoring this issue for some time, to see if we catch some other misbehaviors.
Hit another instance on #119666
Console log: 'System.Security.Cryptography.Tests' from job 11bc29de-540f-459c-985d-8372009d0fc6 workitem ae0f0b0e-2256-4d0c-8bcd-1a7091d3e301 (ubuntu.2204.amd64.android.29.open.svc) executed on machine a001SM8 running Linux-6.8.0-1031-azure-x86_64-with-glibc2.35
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1146782&view=logs&j=d2662c5d-2295-5cda-9ba6-af0bc2edd8b5&t=36dd21ca-62d0-56c6-8b4b-9b795819c96aFrom the adb diagnostic logs
[21:49:12] dbug: ADBRunner using ADB.exe supplied from /datadisks/disk1/work/A996091E/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25405.1/tools/net8.0/any/../../../runtimes/any/native/adb/linux/adb [21:49:12] dbug: Full resolved path:'/datadisks/disk1/work/A996091E/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25405.1/runtimes/any/native/adb/linux/adb' [21:49:12] info: Will attempt to find device supporting architectures: 'x86_64' [21:49:12] dbug: Executing command: '/datadisks/disk1/work/A996091E/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25405.1/runtimes/any/native/adb/linux/adb start-server' [21:49:13] dbug: [21:49:13] info: Finding attached devices/emulators... [21:49:13] dbug: Executing command: '/datadisks/disk1/work/A996091E/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25405.1/runtimes/any/native/adb/linux/adb devices -l' [21:49:13] dbug: Found 1 possible devices [21:49:13] 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:49:13] dbug: Executing command: '/datadisks/disk1/work/A996091E/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25405.1/runtimes/any/native/adb/linux/adb -s emulator-5554 shell getprop ro.product.cpu.abilist' [21:49:13] fail: No attached device supports one of required architectures x86_64 [21:49:13] dbug: No suitable devices found [21:49:13] crit: Failed to find compatible device: x86_64 [21:49:13] dbug: Saving diagnostics data to '/datadisks/disk1/work/A996091E/w/B5700986/e/diagnostics.json' XHarness exit code: 81 (DEVICE_NOT_FOUND)Hit the
DEVICE_NOT_FOUNDfailure again in https://dev.azure.com/dnceng-public/public/_build/results?buildId=1175493&view=results. Failure log: https://helixr1107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-sbomer-naot-androidfa2e9dba3b01454994/System.Xml.Linq.Events.Tests.Attempt.3/1/console.618b10d7.log?helixlogtype=result&skoid=8eda00af-b5ec-4be9-b69b-0919a2338892&sktid=72f988bf-86f1-41af-91ab-2d7cd011db47&skt=2025-10-15T20%3A39%3A52Z&ske=2025-10-15T21%3A39%3A52Z&sks=b&skv=2024-11-04&sv=2024-11-04&se=2025-10-15T21%3A39%3A52Z&sr=b&sp=rl&sig=ziLLWsEwTbCy8D6Zqq56DnWtUz2xK8qEpdrkSG09fxU%3D++ xharness android test --app System.Xml.Linq.Events.Tests.apk --output-directory /datadisks/disk1/work/B51E0945/w/B9150A16/uploads --timeout 00:30:00 --package-name net.dot.System.Xml.Linq.Events.Tests -v --instrumentation net.dot.MonoRunner ++ dotnet exec /datadisks/disk1/work/B51E0945/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25475.1/tools/net8.0/any/Microsoft.DotNet.XHarness.CLI.dll android test --app System.Xml.Linq.Events.Tests.apk --output-directory /datadisks/disk1/work/B51E0945/w/B9150A16/uploads --timeout 00:30:00 --package-name net.dot.System.Xml.Linq.Events.Tests -v --instrumentation net.dot.MonoRunner + sleep 2280 + wait 2335 [10.0.0-prerelease.25475.1+d9aba438cae0eb814085c71dd6caa19e99c8e052] XHarness command issued: android test --app System.Xml.Linq.Events.Tests.apk --output-directory /datadisks/disk1/work/B51E0945/w/B9150A16/uploads --timeout 00:30:00 --package-name net.dot.System.Xml.Linq.Events.Tests -v --instrumentation net.dot.MonoRunner [20:17:53] dbug: ADBRunner using ADB.exe supplied from /datadisks/disk1/work/B51E0945/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25475.1/tools/net8.0/any/../../../runtimes/any/native/adb/linux/adb [20:17:53] dbug: Full resolved path:'/datadisks/disk1/work/B51E0945/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25475.1/runtimes/any/native/adb/linux/adb' [20:17:53] info: Will attempt to find device supporting architectures: 'x86_64' [20:17:53] dbug: Executing command: '/datadisks/disk1/work/B51E0945/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25475.1/runtimes/any/native/adb/linux/adb start-server' [20:17:53] dbug: [20:17:53] info: Finding attached devices/emulators... [20:17:53] dbug: Executing command: '/datadisks/disk1/work/B51E0945/p/microsoft.dotnet.xharness.cli/10.0.0-prerelease.25475.1/runtimes/any/native/adb/linux/adb devices -l' [20:17:53] dbug: No attached devices found Exit code: 0 Std out: List of devices attached...
[20:19:24] dbug: All 9 retries of action failed [20:19:24] 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. [20:19:24] dbug: No suitable devices found [20:19:24] crit: Failed to find compatible device: x86_64 [20:19:24] dbug: Saving diagnostics data to '/datadisks/disk1/work/B51E0945/w/B9150A16/e/diagnostics.json' XHarness exit code: 81 (DEVICE_NOT_FOUND)Looks like some host machines don't have a x64 emulator installed. I will reach out to engineering team.
Reacted by Sven Boemer
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=953058
Build error leg or test failing:
Android.Device_Emulator.JIT.TestFound in: #112547
Error log
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
Summary