Fixed
Status Update
Comments
cc...@google.com <cc...@google.com> #2
Thanks for providing an example -- this is now fixed in 1.0.0-alpha05
ma...@google.com <ma...@google.com>
cc...@google.com <cc...@google.com> #3
Thanks for filing this -- this is now fixed in 1.0 alpha 5.
ma...@google.com <ma...@google.com>
cc...@google.com <cc...@google.com>
ap...@google.com <ap...@google.com> #4
Android 11 samsung c9pro
ap...@google.com <ap...@google.com> #5
Project: platform/frameworks/support
Branch: androidx-main
commit 2189e12ba790617267b4ee81923553ffcc71e90d
Author: Chris Craik <ccraik@google.com>
Date: Fri Jul 14 16:21:41 2023
Add error suggesting emulator update if compile reset fails
Bug: 282191686
Test: CompilationModeTest
Relnote: "Added detail to compilation reset failure to suggest
updating emulator, as some emulators have recently fixed this issue."
Change-Id: I8c81570e0b2e03b9f6453e13f0706b10f59f0455
M benchmark/benchmark-macro/src/main/java/androidx/benchmark/macro/CompilationMode.kt
M benchmark/integration-tests/macrobenchmark/src/main/java/androidx/benchmark/integration/macrobenchmark/CompilationModeTest.kt
https://android-review.googlesource.com/2657262
Branch: androidx-main
commit 2189e12ba790617267b4ee81923553ffcc71e90d
Author: Chris Craik <ccraik@google.com>
Date: Fri Jul 14 16:21:41 2023
Add error suggesting emulator update if compile reset fails
Bug: 282191686
Test: CompilationModeTest
Relnote: "Added detail to compilation reset failure to suggest
updating emulator, as some emulators have recently fixed this issue."
Change-Id: I8c81570e0b2e03b9f6453e13f0706b10f59f0455
M benchmark/benchmark-macro/src/main/java/androidx/benchmark/macro/CompilationMode.kt
M benchmark/integration-tests/macrobenchmark/src/main/java/androidx/benchmark/integration/macrobenchmark/CompilationModeTest.kt
cc...@google.com <cc...@google.com>
na...@google.com <na...@google.com> #6
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.benchmark:benchmark-common:1.2.0-beta02
androidx.benchmark:benchmark-junit4:1.2.0-beta02
androidx.benchmark:benchmark-macro:1.2.0-beta02
Description
Since fixes are slow to roll out, we should have benchmark clearly tell people they're using unsupported emulators if they run into the following bugs:
For the tracing issue, if perfetto capture start fails, do something like:
And add something similar for the compilation failure.