JMR-dev/LibreMail
1
0
Fork 0
Code Issues 40 Pull Requests 2 Actions Packages Projects Releases 2 Wiki Activity

build(gmd): cap managed-device emulators to 1 concurrent (serial) to avoid local VT-x contention #267

Merged
JMR-dev merged 1 commits from build-gmd-serial-emulators into main 2026-07-03 21:48:57 +00:00
Conversation 0 Commits 1 Files Changed 1
+11
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
gradle.properties
+11
View File
@@ -9,3 +9,14 @@ android.useAndroidX=true
# Kotlin (built-in Kotlin is enabled by default in AGP 9; the Kotlin version is set
# via the buildscript classpath in the root build.gradle.kts).
kotlin.code.style=official
# Gradle Managed Devices (app/build.gradle.kts `testOptions.managedDevices`): cap the number
# of emulators Gradle boots at once to 1. The `e2e` device group spans api29-36 and
# org.gradle.parallel=true is on, so without this cap a local `e2eGroupDebugAndroidTest` (or
# the /preflight skill) can launch several emulators concurrently; they contend for the same
# hardware VT-x/HAXM virtualization slot and hang at 0% CPU ("another emulator instance is
# running"). This forces GMD emulator runs to be serial on a single machine. Does not affect
# CI: the `e2e` matrix in .github/workflows/ci.yml runs each API level's emulator on its own
# GitHub Actions runner via reactivecircus/android-emulator-runner + connectedDebugAndroidTest,
# not via these Gradle Managed Device tasks, so this cap has no effect there either way.
android.experimental.testOptions.managedDevices.maxConcurrentDevices=1