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: Macrobenchmark Version used: 1.2.0-alpha05 Devices/Android versions reproduced on: PixelWatch
I'm using macrobenchmark to collect consistent profiling sessions. While I typically have some custom trace markers in the code I want to measure, if I run the same test scenarios against a similar app without those markers it fails.
I can use FrameTimingMetric or StartupTimingMetric, but ideally I could skip them to avoid something that might fail.
It would be good to have some Metric as a placeholder for None. Or alternatively some other generic metric such as Total CPU time that would always be relevant.