Assigned
Status Update
No update yet.
Comments
cc...@google.com
When I run Macrobenchmark via the `connectedCheck` target with info logs on, I can see the arg being set:
```
INFO: Configuring Android Instrumentation driver: android_instrumentation_runtime {
instrumentation_info {
...
args_map {
key: "androidx.benchmark.suppressErrors"
value: "DEBUGGABLE"
}
}
}
```
Attempted to pass the flag via the `-e` option to the `instrument` command of ADB, but no change to error output:
```
$ adb shell am instrument -w com.ring.benchmark/androidx.test.runner.AndroidJUnitRunner -e androidx.benchmark.suppressErrors DEBUGGABLE
...
ERROR: Benchmark Target is Debuggable
```
```
INFO: Configuring Android Instrumentation driver: android_instrumentation_runtime {
instrumentation_info {
...
args_map {
key: "androidx.benchmark.suppressErrors"
value: "DEBUGGABLE"
}
}
}
```
Attempted to pass the flag via the `-e` option to the `instrument` command of ADB, but no change to error output:
```
$ adb shell am instrument -w com.ring.benchmark/androidx.test.runner.AndroidJUnitRunner -e androidx.benchmark.suppressErrors DEBUGGABLE
...
ERROR: Benchmark Target is Debuggable
```
Description
Component used: Microbenchmark (Not tried macro) Version used: 1.1.1 Devices/Android versions reproduced on: Emulator and Pixel 4a at 13
According tohttps://developer.android.com/topic/performance/benchmarking/benchmarking-in-ci#save_and_locate_the_files , running the
:benchmarkReporttask should place the results back on the host machine. Indeed, running that task, I see:However, that dir is empty. That's true with a device connected or running on emulator (with the appropriate
androidx.benchmark.suppressErrorsflag set).If I run, on the command line, what Studio executes (ie
:connectedReleaseAndroidTest) then I do get results on my machine (located in the above path), but upon completion of that task it doesn't mention anything about that resulting location.So I guess I'm not blocked given I do get output, but given that
:benchmarkReportsays:I'd assume that that's the task I should be running (and that it's not doing what it seems to say it should)?