Fix Android emulator CI by replacing action with manual startup

[Copilot]

Summary

The Android emulator CI job was failing due to device detection timeouts with the reactivecircus/android-emulator-runner@v2 action. Replaced with manual emulator startup providing explicit control over device initialization and boot verification.

Changes

Install Android dependencies

• Install emulator and system images via sdkmanager
• Move cmdline-tools to proper SDK structure ($ANDROID_HOME/cmdline-tools/latest)
• Add path validation before operations

Replace GitHub Action with manual steps

• Create AVD explicitly (cached between runs)
• Start emulator with optimized flags: -no-snapshot-load, -no-boot-anim, -gpu swiftshader_indirect
• Two-phase boot detection:
  1. Wait for device visibility in adb devices
  2. Poll sys.boot_completed property until 1
• Add diagnostic step listing connected devices
• Extract device ID to EMULATOR_DEVICE_ID environment variable

Wait loop

for i in {1..90}; do
  if ! adb devices | grep -q "$EMULATOR_DEVICE_ID"; then
    sleep 10
    continue
  fi
  boot_completed=$(adb -s $EMULATOR_DEVICE_ID shell getprop sys.boot_completed 2>/dev/null | tr -d '\r')
  [[ "$boot_completed" == "1" ]] && break
  sleep 10
done

Test plan

YAML syntax validated. Changes follow standard Android emulator CI patterns. Will be validated by CI run.

Original prompt

Problem Description

The CI job for the Android emulator in the pull workflow is currently failing. The logs show multiple attempts to use adb to communicate with the emulator (device emulator-5554), but these fail because the device is not detected, resulting in the error device 'emulator-5554' not found. The script eventually times out while waiting for the emulator to boot.

Root Cause

• The emulator for the specified AVD fails to start properly, or the job script does not wait long enough for the emulator to complete its boot sequence.
• The AVD configuration might be missing or improperly set up.
• Debugging steps like checking available devices (adb devices) and logging emulator output were not included, making it harder to identify the specific issue.

Proposed Solution

1. Update the workflow configuration to ensure that the emulator starts correctly by explicitly invoking the emulator with appropriate flags.
2. Add a wait loop to verify the emulator boot completion before running any tests or adb commands.
3. Include diagnostic commands to capture emulator and adb state for debugging purposes.

Code Changes

Modify .github/workflows/pull.yml

Insert the following steps into the appropriate section for starting the Android emulator:

- name: Start Emulator
  run: |
    $ANDROID_HOME/emulator/emulator -avd test_avd -no-snapshot-load -no-window -gpu swiftshader_indirect -no-boot-anim &
    adb start-server
    for i in {1..90}; do
        boot_completed=$(adb -s emulator-5554 shell getprop sys.boot_completed 2>/dev/null | tr -d '\r')
        if [[ "$boot_completed" == "1" ]]; then
            echo "Emulator booted."
            break
        fi
        echo "Waiting for emulator to boot..."
        sleep 2
    done

- name: Check Devices
  run: adb devices

Improvements

• The -no-snapshot-load and -no-boot-anim flags optimize emulator startup.
• The waiting loop ensures the emulator is fully booted before proceeding.
• Diagnostic steps make it easier to debug potential issues in the future.

This pull request was created from Copilot chat.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/16350

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• ROCm linux.rocm.gpu.gfx942.*.b runners switching providers

❌ 3 New Failures, 1 Unrelated Failure

As of commit f14088a with merge base 09bdad7 ():

NEW FAILURES - The following jobs have failed:

• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t 04f6f5f05d16d29918904d6e410821b6552822f63aafe2908534d2d2dec21086 /exec failed with exit code 1
• pull / unittest-arm-backend-with-no-fvp (test_pytest_ops) / linux-job (gh)
  RuntimeError: Command docker exec -t c935f2bb25aa89f1e94081dcd634e6d76696eb33dc24d467b2fc03684e47eeb5 /exec failed with exit code 1
• Test CUDA Builds / test-model-cuda-e2e (mistralai, Voxtral-Mini-3B-2507, quantized-int4-tile-packed) / linux-job (gh)
  RuntimeError: Command docker exec -t 5dfca4c42eaa7c2a6e424c4cc1b437093f9447fad3ec9b1dbf40de9ee305fd3a /exec failed with exit code 1

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

• pull / android / run-emulator (gh) (#16137)
  Process completed with exit code 1.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-cla]

Hi @Copilot!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.