Status Update
No update yet.
Comments
hu...@google.com
I am not sure I understand the use case. how can the benchmark be code to real world scenario when it's not possible to do right now ? which scenario is it ?
In any case, since this would be for benchmarking, this would clearly not be available through the public DSL. We should find a semi-private way of doing this (maybe the private variant API object could offer that functionality for instance or a property).
da...@google.com
an...@google.com
We want benchmarks to measure code after Progaurd / R8, but it's not possible to turn that on for androidTests in library modules at the moment (to my knowledge?)
Benchmarks are also a public facing thing, but we have a plugin to help configure gradle builds for our users, so if support for this ends up in a private API, we could try to keep those usages localized to our code perhaps.
Description
android.experimental.testOptions.managedDevices.maxConcurrentDevices=1should 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
lockfor the device count while running the tests is not kept while the tests are actually running:The
usedoes not extend to the call torunUtpWithRetryForEmulatorTimeoutException, which looks to be what runs the tests: