Fixed
Status Update
Comments
sj...@google.com <sj...@google.com>
cc...@google.com <cc...@google.com>
ap...@google.com <ap...@google.com> #2
Project: platform/frameworks/support
Branch: androidx-main
commit 3d83f48e67e0b73feea1d5d677b7a047a15150f6
Author: Chris Craik <ccraik@google.com>
Date: Wed Apr 19 16:49:14 2023
Fix GPU clock locking to use correct equality check
Test: benchmark/gradle-plugin/src/main/resources/scripts/lockClocks.sh # tested on device that can't be locked, but verified branch with logging
Fixes: 213935715
Relnote: Fix GPU clock locking script to compare strings correctly
Change-Id: I53e5416ca2b24933a3d6d43db678dad035132dd2
M benchmark/gradle-plugin/src/main/resources/scripts/lockClocks.sh
https://android-review.googlesource.com/2548631
Branch: androidx-main
commit 3d83f48e67e0b73feea1d5d677b7a047a15150f6
Author: Chris Craik <ccraik@google.com>
Date: Wed Apr 19 16:49:14 2023
Fix GPU clock locking to use correct equality check
Test: benchmark/gradle-plugin/src/main/resources/scripts/lockClocks.sh # tested on device that can't be locked, but verified branch with logging
Fixes: 213935715
Relnote: Fix GPU clock locking script to compare strings correctly
Change-Id: I53e5416ca2b24933a3d6d43db678dad035132dd2
M benchmark/gradle-plugin/src/main/resources/scripts/lockClocks.sh
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-gradle-plugin:1.2.0-alpha14
Description
The version used:https://developer.android.com/jetpack/androidx/releases/benchmark#1.1.0-alpha13
Devices/Android versions reproduced on: blueline based on Android 12
Running .\gradlew.bat lockClocks command couldn't lock the GPU frequency. The related log is shown as below: Unable to lock gpu clocks of AOSP on blueline (blueline).
384 if [ "$DEVICE" -ne "wembley" ]; then
Please correct the "-ne" operators.