IssueTracker

Component used: androidx.baselineprofile Version used:1.2.4

Summary:

I want to execute the generateBaselineProfile task created through the Baseline Profile plugin in GitHub Actions, so that the Baseline Profile is automatically updated every time it's merged into a specific branch.

The runner is a server using CentOS 7, and in GitHub Actions, I am running the steps as follows:

jobs:
  auto-update-baseline-profile:
    runs-on: [ self-hosted ]

    steps:
      - name: Checkout to HEAD
        uses: actions/checkout@v3

      - name: Set up JDK 17
        uses: actions/setup-java@v3
        with:
          java-version: 17
          distribution: 'temurin'

      - name: Setup Android SDK
        uses: android-actions/setup-android@v3

      - name: Grant execute permission for gradlew
        run: chmod +x gradlew

      - name: Clean Managed Devices
        run: ./gradlew cleanManagedDevices --unused-only

      - name: Generate Baseline Profile
        run: ./gradlew :app:mobile:generateRealReleaseBaselineProfile 
          -Pandroid.testoptions.manageddevices.emulator.gpu="swiftshader_indirect" 
          -Pandroid.testInstrumentationRunnerArguments.androidx.benchmark.enabledRules=BaselineProfile

And the managed device settings are as follow...

    testOptions.managedDevices.devices {
        create<ManagedVirtualDevice>("pixel6Api34") {
            device = "Pixel 6"
            apiLevel = 34
            systemImageSource = "aosp"
        }
    }

And I got this error at "Generate Baseline Profile" step.

* What went wrong:
Execution failed for task ':baselineprofile-mobile:pixel6Api34Setup'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.ManagedDeviceInstrumentationTestSetupTask$ManagedDeviceSetupRunnable
   > java.lang.IllegalStateException: Gradle was not able to complete device setup for: dev34_default_x86_64_Pixel_6
     The emulator failed to open the managed device to generate the snapshot.
     This is because the emulator closed unexpectedly, try updating the emulator and
     ensure a device can be run from Android Studio.

Is there any workaround so far??