Repository navigation
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5795 +/- ##
==========================================
- Coverage 76.13% 76.12% -0.02%
==========================================
Files 528 528
Lines 19579 19579
Branches 3829 3829
==========================================
- Hits 14906 14904 -2
- Misses 3791 3792 +1
- Partials 882 883 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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. The standard runner has less disk, so the jobs print the free space before and after. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ric-oliv
force-pushed
the
ci/run-android-device-tests-on-standard-runners
branch
from
October 24, 2026 18:15
b129a52 to
a667215
Compare
This was referenced Oct 24, 2026
This branch has not been deployed
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.
The four Android emulator jobs run on
ubuntu-latest-4-cores, a larger runner, and each of them takes 15 to 23 minutes on a normal run.#2139 moved them there in March 2023, because back then the 2-core standard Linux runners couldn't run a hardware-accelerated emulator. That has changed:
udevrule this workflow already sets in "Enable KVM group perms".ubuntu-latesthas 4 CPUs and 16 GB of RAM, the same cores as the larger runner.This PR moves the emulator jobs to
ubuntu-latest. The standard runner has less disk, and these jobs also install workloads and build the integration test app next to a 4 GB emulator disk, so each job prints the free space at the start and the end.Measured on the first run, against the last 10 runs on the larger runner. All four emulator jobs passed on
ubuntu-latest, in the default "GitHub Actions" runner group:ubuntu-latest-4-cores, last 10 runsubuntu-latest, this PRSo the emulator and the tests run just as fast on the standard runner, the jobs start within seconds instead of waiting for a larger runner, and the disk has plenty of room. The docs list 14 GB, but the runner has 145.
This run took 60 minutes, because Setup Environment hit the slow Mono download in 4 of the 6 jobs, taking 11.9 to 20.3 minutes. That's the download #5794 removes, and it hits both runner types.
#skip-changelog