Fixed
Status Update
Comments
jg...@google.com <jg...@google.com>
ap...@google.com <ap...@google.com> #2
Project: platform/frameworks/support
Branch: androidx-main
Author: Chris Craik <
Link:
Add androidx.benchmark.measureRepeatedOnMainThread.throwOnDeadline
Expand for full commit details
Add androidx.benchmark.measureRepeatedOnMainThread.throwOnDeadline
Test: Manual (test requires breaking abstractions and running for > 10 seconds)
Fixes: 353226476
Relnote: "Added
androidx.benchmark.measureRepeatedOnMainThread.throwOnDeadline, which
can be set to false to disable the throw on deadline behavior of
measureRepeatedOnMainThread for local testing. Not otherwise
recommended, as this increase likelihood of ANRs during tests."
Change-Id: Idbeecc1394b11395946d6e2bdf4187940a1099a0
Files:
- M
benchmark/benchmark-common/src/main/java/androidx/benchmark/Arguments.kt
- M
benchmark/benchmark-junit4/src/main/java/androidx/benchmark/junit4/BenchmarkRule.kt
Hash: 5e3b4119650c81dda0d4c4faa96728185d35e291
Date: Thu Dec 05 16:46:08 2024
na...@google.com <na...@google.com> #3
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.benchmark:benchmark-common:1.4.0-alpha07
androidx.benchmark:benchmark-junit4:1.4.0-alpha07
Description
I'm using aosp/3162520 for making Compose microbenchmarks debuggable with the Android Studio debugger. That includes changes in change in BenchmarkRule to disable the hard deadline, as otherwise the following exception is thrown during debugging:
build.gradle
andAndroidManifest
in the Compose package. I also had to make aWould it be possible to add an instrumentation argument to disable the deadlines?