Skip to content

Change runner environment for Android emulator #16614

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kirklandsign merged 3 commits into from
Jan 15, 2026
Merged

Change runner environment for Android emulator #16614

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5f707d2
Change runner environment for Android emulator
kirklandsign Jan 15, 2026
d13ad43
Change runner type for Android emulator job
kirklandsign Jan 15, 2026
8b7ac89
Update .github/workflows/_android.yml
kirklandsign Jan 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/_android.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,8 +51,8 @@ jobs:
# Running Android emulator directly on the runner and not using Docker
run-emulator:
needs: build-llm-demo
# NB: Use metal install for KVM support to run the emulator faster
runs-on: linux.24xl.spr-metal
# NB: This job runs on the shared 8-core-ubuntu runner; KVM / bare-metal assumptions no longer apply
runs-on: 8-core-ubuntu
Copy link

Copilot AI Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The runner change from linux.24xl.spr-metal (bare-metal with KVM support) to 8-core-ubuntu (shared virtualized runner) will significantly impact Android emulator performance. The emulator is configured to use 6 cores and 16GB RAM (lines 122-123), and the comment at line 110 mentions 10-minute cold boot times. On a shared virtualized runner without KVM acceleration, emulator boot times and test execution could be substantially longer, potentially causing timeouts. Consider: 1) reducing the emulator-boot-timeout (line 129) if testing shows improved performance, or increasing it if timeouts occur, 2) verifying the shared runner has sufficient memory for the 16GB RAM allocation, and 3) monitoring job duration after this change.

Copilot uses AI. Check for mistakes.
env:
ANDROID_NDK_VERSION: r28c
API_LEVEL: 34
Expand Down
Loading