Open akoeplinger opened 11 months ago
fyi @dougbu this seems to be catching cases when Android emulators are not booted properly
Not sure why the result validation doesn't match, do we need to set up something special to monitor the runtime-extra-platforms pipeline?
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.
https://github.com/dotnet/dnceng/issues/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.
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: https://github.com/dotnet/dnceng/issues/1467
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❕
@akoeplinger how are things going w/ your fix attempt(s)❔
I just came back from vacation, will take another stab at this early next week :)
Build
https://dev.azure.com/dnceng-public/public/_build/results?buildId=472093
Build leg reported
android-x86 Release AllSubsets_Mono
Pull Request
https://github.com/dotnet/runtime/pull/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
@dotnet/dnceng
Release Note Category
Release Note Description
Additional information about the issue reported
No response
Known issue validation
Build: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=472093 Error message validated:
Did not detect boot completion variable on device
Result validation: :x: Known issue did not match with the provided build. Validation performed at: 11/20/2023 10:43:09 AM UTCReport
Summary