Runner hangs installing build tools

Today I noticed that the runner hangs while trying to install latest build tools.

Run reactivecircus/android-emulator-runner@v2
  with:
    api-level: 29
    profile: pixel
    script: ./gradlew app:connectedDevDebugAndroidTest domain:connectedDebugAndroidTest
    target: default
    arch: x86
    avd-name: test
    emulator-options: -no-window -gpu swiftshader_indirect -no-snapshot -noaudio -no-boot-anim
    disable-animations: true
API level: 29
target: default
CPU architecture: x86
Hardware profile: pixel
SD card path or size: 
AVD name: test
emulator options: -no-window -gpu swiftshader_indirect -no-snapshot -noaudio -no-boot-anim
disable animations: true
Script:
./gradlew app:connectedDevDebugAndroidTest domain:connectedDebugAndroidTest
Installing new cmdline-tools.
/usr/bin/unzip -q /Users/buildmachine/actions-runner/OrgWideRunner/_work/_temp/7caea691-806e-4246-be51-fb6e7a29e145
Installing latest build tools, platform tools, and platform.
/bin/sh -c \sdkmanager --install 'build-tools;30.0.3' platform-tools 'platforms;android-29' > /dev/null

Back from holidays so I’m not sure when it stopped working.

This is the job as I have in my workflow.

  instrumentation_test:
    needs: unit_test
    runs-on: [self-hosted, macos, android]
    steps:
      - name: Checkout Repo
        uses: actions/checkout@v2
        with:
          fetch-depth: 0
      - name: Run Instrumentation Tests on Emulator
        uses: reactivecircus/android-emulator-runner@v2
        with:
          api-level: 29
          profile: pixel
          script: ./gradlew app:connectedDevDebugAndroidTest

      - name: Archive Instrumentation Test Results
        if: ${{ always() }}
        uses: actions/upload-artifact@v1
        with:
          name: Instrumentation Test Results
          path: ./app/build/reports

[ychescale9]

TBH I haven’t tested or used this action with self-hosted runners myself so I haven’t really been considering potential issues with self-hosted runners when making changes.

I think adding a check for $ANDROID_SDK_ROOT makes sense, but for self-hosted runners there are likely to be other requirements in the host VM that we should check if we want to support self-hosted runners properly.

I’ll think about this for a bit.

[sapuglha]

Indeed that did the trick. I manually added ANDROID_SDK_ROOT to the .env for the runner and it worked. I will need to consult whoever configured the runner to see if I should instead add it elsewhere or we’re risking it going away by some automated update or service restart.

I wonder if adding a check for $ANDROID_SDK_ROOT in the scripts would be valuable, since this change requires it and would hang the action otherwise.

Thanks for your help!