Skip to content

fix(ci): fix android emulator OOM on CI#40

Open
CAMOBAP wants to merge 1 commit into
mainfrom
fix/android-emulator-oom
Open

fix(ci): fix android emulator OOM on CI#40
CAMOBAP wants to merge 1 commit into
mainfrom
fix/android-emulator-oom

Conversation

@CAMOBAP

@CAMOBAP CAMOBAP commented Jun 25, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Switch target: google_apistarget: default — AOSP image doesn't bundle Play Services, uses ~600MB less RAM and boots faster. Harness tests don't need Play Services.
  • Add ./gradlew --stop before launching the emulator — kills the resident Gradle daemon after the build, freeing ~1GB of heap before the emulator claims its 2560MB.

Root cause

The emulator process was silently OOM-killed immediately after launch — it never responded to a single adb poll over the full 600s boot timeout. The google_apis image bumped RAM to 2560MB, and with two live Gradle/Java daemons still running after the build step, the 7GB ubuntu-latest runner had insufficient memory left.

Test plan

  • harness-android job boots emulator and completes without timeout

🤖 Generated with Claude Code

…emon before boot

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant