You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
aarch64 Android 3.14 failed with "Unable to start Android emulator (...) Selected GPU option 'auto-no-window' is not valid" #162247
Unable to start Android emulator for dev35_aosp_atd_arm64-v8a_Small_Phone. Error message from emulator process = [ERROR | gpuChoiceBasedOnGpuOptions: Selected GPU option 'auto-no-window' is not valid, switching to 'auto' mode.]
3.14 logs:
(...)
> Task :app:createDebugAndroidTestApkListingFileRedirect
> Task :app:packageDebug
> Task :app:createDebugApkListingFileRedirect
> Task :app:maxVersionDebugAndroidTest FAILED
> Task :app:mergeDebugAndroidTestTestResultProtos
Test execution completed. See the report at: file:///Users/android/buildarea/3.14.mhsmith-android-aarch64/build/Android/testbed/app/build/reports/androidTests/managedDevice/debug/allDevices/index.html
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:maxVersionDebugAndroidTest' (registered by plugin 'com.android.internal.application').
> java.util.concurrent.ExecutionException: com.android.build.gradle.internal.AvdSnapshotHandler$EmulatorStartFailedException: Unable to start Android emulator for dev35_aosp_atd_arm64-v8a_Small_Phone. Error message from emulator process = [ERROR | gpuChoiceBasedOnGpuOptions: Selected GPU option 'auto-no-window' is not valid, switching to 'auto' mode.]
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights from a Build Scan (powered by Develocity).
> Get more help at https://help.gradle.org.
BUILD FAILED in 43s
75 actionable tasks: 75 executed
Yes, it looks like when an Android buildbot runs out of disk space (or host RAM), the emulator snapshot can get corrupted and give all kinds of different errors on subsequent runs.
Activity
vstinner commentedon Nov 18, 2026
cc @mhsmith
mhsmith commentedon Nov 18, 2026
This was caused by the buildbot running out of disk space, which is now fixed as discussed in python/buildmaster-config#833.
vstinner commentedon Nov 19, 2026
Oh, good that it's already fixed! Sadly, logs didn't give any hint about disk full :-(
freakboy3742 commentedon Nov 19, 2026
Hrm… time to spelunk to see where the disk space has gone...
mhsmith commentedon Nov 19, 2026
Yes, it looks like when an Android buildbot runs out of disk space (or host RAM), the emulator snapshot can get corrupted and give all kinds of different errors on subsequent runs.