Repository navigation
ci: run the Android emulator jobs on standard runners - #5812
Merged
Merged
Conversation
This was referenced Oct 25, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5812 +/- ##
=======================================
Coverage 76.13% 76.13%
=======================================
Files 528 528
Lines 19579 19579
Branches 3829 3829
=======================================
Hits 14906 14906
Misses 3791 3791
Partials 882 882 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
ric-oliv
force-pushed
the
ci/test-unsupported-aot-in-build-legs
branch
from
October 25, 2026 16:22
1f30f05 to
a807d74
Compare
ric-oliv
force-pushed
the
ci/run-android-emulators-on-standard-runners
branch
from
October 25, 2026 16:22
a638f15 to
4bfc23a
Compare
ric-oliv
marked this pull request as ready for review
October 26, 2026 19:05
ric-oliv
force-pushed
the
ci/run-android-emulators-on-standard-runners
branch
from
October 26, 2026 19:15
4bfc23a to
e180542
Compare
ric-oliv
force-pushed
the
ci/test-unsupported-aot-in-build-legs
branch
from
October 26, 2026 19:15
a807d74 to
44331a8
Compare
Comment on lines
+101
to
+102
| # Standard Linux runners support hardware-accelerated emulators since 2024, with the KVM step below: | ||
| # https://github.blog/changelog/2024-04-02-github-actions-hardware-accelerated-android-virtualization-now-available/ |
Collaborator
There was a problem hiding this comment.
Suggested change
| # Standard Linux runners support hardware-accelerated emulators since 2024, with the KVM step below: | |
| # https://github.blog/changelog/2024-04-02-github-actions-hardware-accelerated-android-virtualization-now-available/ |
Seems like that explanation belongs in the PR description - not the code.
Comment on lines
+180
to
+181
| # Standard Linux runners support hardware-accelerated emulators since 2024, with the KVM step below: | ||
| # https://github.blog/changelog/2024-04-02-github-actions-hardware-accelerated-android-virtualization-now-available/ |
Collaborator
There was a problem hiding this comment.
Suggested change
| # Standard Linux runners support hardware-accelerated emulators since 2024, with the KVM step below: | |
| # https://github.blog/changelog/2024-04-02-github-actions-hardware-accelerated-android-virtualization-now-available/ |
Same again...
ric-oliv
force-pushed
the
ci/test-unsupported-aot-in-build-legs
branch
from
October 27, 2026 09:30
44331a8 to
0552c5b
Compare
ric-oliv
force-pushed
the
ci/run-android-emulators-on-standard-runners
branch
from
October 27, 2026 09:39
e180542 to
201079d
Compare
github-actions
Bot
added
risk: low
bitsandfoxes
approved these changes
Oct 27, 2026
ric-oliv
force-pushed
the
ci/test-unsupported-aot-in-build-legs
branch
from
October 27, 2026 12:23
0552c5b to
cd1480d
Compare
Base automatically changed from
ci/test-unsupported-aot-in-build-legs
to
main
October 27, 2026 12:23
The emulator jobs ran on the ubuntu-latest-4-cores larger runner. #2139 moved them there in 2023 because the 2-core standard runners couldn't run a hardware-accelerated emulator. Since April 2024 they can, with the same KVM udev rule this workflow already sets, and on public repositories ubuntu-latest now has 4 CPUs and 16 GB of RAM. Both the device test and the integration test jobs move. On the first runs the device tests took 2.5 to 4.5 minutes, against 2.3 to 4.4 on the larger runner, with the same 2,921 tests. The standard runner listed less disk, but had 88 GB free at the start and 67 at the end. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ric-oliv
force-pushed
the
ci/run-android-emulators-on-standard-runners
branch
from
October 27, 2026 12:24
201079d to
395af6d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part 6 of 6 for #5806, based on #5811. The Android emulator jobs run on
ubuntu-latest-4-cores, a larger runner. #2139 moved them there in March 2023, because the 2-core standard Linux runners couldn't run a hardware-accelerated emulator then. Since April 2024 they can, with the same KVMudevrule this workflow already sets. On public repositories,ubuntu-latesthas 4 CPUs and 16 GB of RAM. So both emulator jobs, the device tests and the integration tests, move toubuntu-latest.Measured in #5795, against the last 10 runs on the larger runner:
ubuntu-latestOn this PR's own CI
3 runs. Android Device Tests took 17.9, 18.4 and 17.5 minutes. The emulator jobs started within 0.1 minutes of being queued. On #5810, with the same jobs still on the larger runner, they waited up to 11.9, 25.6 and 20.5 minutes for one. Run Tests took 2.3 to 3.5 minutes here, against 2.8 to 3.5 there. The whole stack's numbers are in #5806.
Closes #5806
#skip-changelog