Skip to content

aarch64 Android 3.14 failed with "Unable to start Android emulator (...) Selected GPU option 'auto-no-window' is not valid" #162247

Closed

Description

@vstinner

Bug report

Error:

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

The 3.15 logs are similar.

CPython versions tested on:

3.14

Operating systems tested on:

Other

Activity

  1. vstinner commented on Nov 18, 2026

    @vstinner
    MemberAuthor
  2. mhsmith commented on Nov 18, 2026

    @mhsmith
    Member

    This was caused by the buildbot running out of disk space, which is now fixed as discussed in python/buildmaster-config#833.

  3. vstinner commented on Nov 19, 2026

    @vstinner
    MemberAuthor

    This was caused by the buildbot running out of disk space, which is now fixed as discussed in python/buildmaster-config#833.

    Oh, good that it's already fixed! Sadly, logs didn't give any hint about disk full :-(

  4. freakboy3742 commented on Nov 19, 2026

    @freakboy3742
    Contributor

    Hrm… time to spelunk to see where the disk space has gone...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    OS-androidtype-bugAn unexpected behavior, bug, or error

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions