Fixed
Status Update
Comments
hu...@google.com <hu...@google.com> #2
I don't think the average developer understands the distinction between method references and method definitions in this context (inside a DEX file). I know I don't.
@jvg, can you elaborate?
da...@google.com <da...@google.com>
an...@google.com <an...@google.com> #3
people who are looking at the bytecode in the dex to optimize their app through shrinking hopefully will learn the difference as string tables for method references between various dex files can account for quite a bit of disk space. but more importantly a definition is something you can analyze its code for where a reference you can't so the UI can be confusing without seeing the difference
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: