Android emulator not booting completely on Helix queue

[akoeplinger]

Build

https://dev.azure.com/dnceng-public/public/_build/results?buildId=472093

Build leg reported

android-x86 Release AllSubsets_Mono

Pull Request

dotnet/runtime#93220

Known issue core information

Fill out the known issue JSON section by following the step by step documentation on how to create a known issue

 {
    "ErrorMessage" : "Did not detect boot completion variable on device",
    "BuildRetry": false,
    "ErrorPattern": "",
    "ExcludeConsoleLog": false
 }

@dotnet/dnceng

Release Note Category

• Feature changes/additions
• Bug fixes
• Internal Infrastructure Improvements

Release Note Description

Additional information about the issue reported

No response

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=472093
Error message validated: Did not detect boot completion variable on device
Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 11/20/2023 10:43:09 AM UTC

Report

Build	Definition	Test	Pull Request
716331	dotnet/arcade	System.Buffers.Tests-x86.WorkItemExecution	dotnet/arcade#14886
713203	dotnet/arcade	System.Buffers.Tests-x64.WorkItemExecution	dotnet/arcade#14870
712600	dotnet/runtime	IntrinsicsInSystemPrivateCoreLib.Tests.WorkItemExecution	dotnet/runtime#103647
710299	dotnet/xharness	System.Numerics.Vectors.Tests-x86.WorkItemExecution
704919	dotnet/xharness	System.Buffers.Tests-x86.WorkItemExecution
702874	dotnet/runtime	IntrinsicsInSystemPrivateCoreLib.Tests.WorkItemExecution
703011	dotnet/runtime	System.Composition.AttributeModel.Tests.WorkItemExecution
702715	dotnet/runtime	System.Diagnostics.Process.Tests.WorkItemExecution
700371	dotnet/runtime	System.Linq.Expressions.Tests.WorkItemExecution
696739	dotnet/runtime	System.Diagnostics.Process.Tests.WorkItemExecution
694253	dotnet/runtime	System.Diagnostics.Process.Tests.WorkItemExecution
690754	dotnet/runtime	System.Linq.Tests.WorkItemExecution
689568	dotnet/arcade	System.Buffers.Tests-x86.WorkItemExecution	dotnet/arcade#14791

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	4	13

[premun]

fyi @dougbu this seems to be catching cases when Android emulators are not booted properly

[akoeplinger]

Not sure why the result validation doesn't match, do we need to set up something special to monitor the runtime-extra-platforms pipeline?

[dougbu]

This feels very similar to #1383 and #1415. The general theme is the emulator isn't starting as quickly as expected (there's a 5 minute loop checking for boot_completed in the XHarness case) or just isn't started. We haven't made much progress on either issue, partially because only @premun knows much about the emulators and he's busy elsewhere.

the ubuntu.2204.amd64.android.29.open queue is one of many we've had problems with when deploying in our staging environment.

I can see how dotnet/xharness#1106 could help here and suggest we keep an eye on this issue for additional hits.

[akoeplinger]

#1383 should be different since that is about Android devices i.e. there's no emulator to start so if they report not booted the device is usually hosed.

If the emulator issue is really about not starting fast enough I think I'd be happy if you add a sleep 5min into the VM provisioning as a quick workaround.

[AlitzelMendez]

Not sure why the result validation doesn't match, do we need to set up something special to monitor the runtime-extra-platforms pipeline?

for this particular question the problem is not the runtime-extra-platforms (we are analyzing it), it is a problem on our side when there are helix work items internal retries, we are not analyzing the logs of all the attempts, created an issue for this: #1467

[dougbu]

I'd be happy if you add a sleep 5min into the VM provisioning as a quick workaround.

there's a 5 minute loop just prior to the failing sys.boot_completed search in the function starting at https://github.com/dotnet/xharness/blob/38841f0f33ca713ca5d6388c681bdd911425b488/src/Microsoft.DotNet.XHarness.Android/AdbRunner.cs#L191

personally, I'm nervous about adding Thread.Sleep(...) in that code b/c @premun seemed confident my similar actions for #1415 (where I extended a loop searching for a different readiness signal) were unhelpful. we found that "fix" only reduced the likelihood of our validation failures; a build soon after my fix went in failed again and we (temporarily❔) gave up

if someone understands dotnet/xharness better, please chime in❕

[dougbu]

@akoeplinger how are things going w/ your fix attempt(s)❔

[akoeplinger]

I just came back from vacation, will take another stab at this early next week :)