-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix linux-ubuntu-android-emulator
validation issues
#1415
Comments
We have temporarily unmonitored the android queues in https://dnceng.visualstudio.com/internal/_git/dotnet-helix-machines/pullrequest/35248, and they should be added back to the deployment list once we're confident we understand the failures/fixes. |
linux-ubuntu-android-emulator
validation issues
@premun any ideas for getting to the root cause of our recent problems w/ the emulators❔ I could imagine creating a VM for one of the failing images before we unmonitored the queues. might have an issue there b/c our |
@akoeplinger is helping us with this. We spoke about this briefly and it seems that as the first step, we would make the Helix SDK collect the emulator log in case a Helix work item doesn't find it booted. We could then take the same emulator log collection command (I don't know what it is myself) and put it in our |
I'm experimenting with https://dev.azure.com/dnceng/internal/_git/dotnet-helix-machines/pullrequest/35535 to see if bumping the timeout to 10mins and moving the waiting logic from validate.sh to the first run script helps. |
Due to changing priorities, Alex is not able to work on this currently. Moving the issue to our backlog. |
Adding an additional 5 minute wait won't work. That causes timeouts during custom script extension execution when the machine is trying to start up. |
Builds of main since #20231102.02 failed consistently when validating the
linux-ubuntu-android-emulator
artefact on variousubuntu.??04.amd64.android.*.open
queues. Problem is reported as... no running emulators at /etc/osob/validate/linux-ubuntu-android-emulator ...
.One possibility: 3 minutes may be insufficient time these days for the emulator(s) to start up.
Release Note Category
Release Note Description
Corrected a problem preventing validation of some of our queues.
The text was updated successfully, but these errors were encountered: