Skip to content

Stabilise the Android emulator: no snapshot, more RAM, reclaim disk #57

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
germ-mark merged 1 commit into from
Aug 18, 2026
Merged

Stabilise the Android emulator: no snapshot, more RAM, reclaim disk #57

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 10 additions & 0 deletions .github/workflows/ci-android.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,3 +26,13 @@ jobs:
uses: skiptools/swift-android-action@v2
with:
swift-version: "6.3"
# The emulator, not the tests, is what fails here: seen twice as
# `adb: device offline` right after "Successfully loaded snapshot",
# and as the adb daemon dying mid-run (exit 137) — never as a failing
# assertion. `-no-snapshot` takes the snapshot save/restore step out
# of the picture at the cost of a slower boot, and the extra memory
# gives the AVD headroom now that the test binary statically links
# libsecp256k1. Reclaiming disk first keeps the Swift toolchain and
# Android SDK from crowding the emulator's own image out.
android-emulator-options: "-no-window -noaudio -no-boot-anim -no-snapshot -memory 4096"
free-disk-space: "true"
Loading