Fixed
Status Update
Comments
hu...@google.com <hu...@google.com> #2
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Canary 2
- Android Gradle Plugin 8.8.0-alpha02
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
da...@google.com <da...@google.com>
an...@google.com <an...@google.com> #3
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Canary 6
- Android Gradle Plugin 8.8.0-alpha06
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
Description
android.experimental.testOptions.managedDevices.maxConcurrentDevices=1
should result in the behavior that no more than one device is active at a time.However, this is not the case: when the tests are running, many devices are spun up to run concurrently. In local testing, I've seen as many as 8 trying to be run at the same time.
When briefly debugging, it looks like the
lock
for the device count while running the tests is not kept while the tests are actually running:The
use
does not extend to the call torunUtpWithRetryForEmulatorTimeoutException
, which looks to be what runs the tests: