Fixed
Status Update
No update yet.
Comments
ja...@google.com
Thanks for the feedback. To help us troubleshoot this issue further, we will need more information. Please share detailed reproduction steps and as much as possible of the following information when it applies if you haven’t already:
1. Android Studio version and OS type and version
2. Screenshots or videos of the issue
3. idea.log file (select Help > Show Log in Finder / Explorer)
4. Thread dumps if the issue is a freezing or non-responding UI.
For more information on what’s needed and how to obtain this information please read the guide athttps://developer.android.com/studio/report-bugs#studio-bugs
1. Android Studio version and OS type and version
2. Screenshots or videos of the issue
3. idea.log file (select Help > Show Log in Finder / Explorer)
4. Thread dumps if the issue is a freezing or non-responding UI.
For more information on what’s needed and how to obtain this information please read the guide at
ma...@textnow.com
Thank you for the reply. I do not think the component is correct, but I did not have permission to put it anywhere else.
This was reproducible under Android Studio, local CLI, and GHA.
The stack trace above is what is output from all 3 scenarios.
The issue is when the `baselineProfile|managedDevices` does not align with `android|testOptions|managedDevices|devices`, then it tells you it can't find the test. The actual issue is that it can't find the device specification.
In BaselineProfileProducerPlugin.kt, the error handling treats all exceptions with the same test error message.
Hope that helps.
This was reproducible under Android Studio, local CLI, and GHA.
The stack trace above is what is output from all 3 scenarios.
The issue is when the `baselineProfile|managedDevices` does not align with `android|testOptions|managedDevices|devices`, then it tells you it can't find the test. The actual issue is that it can't find the device specification.
In BaselineProfileProducerPlugin.kt, the error handling treats all exceptions with the same test error message.
Hope that helps.
rk...@google.com
je...@google.com
ma...@google.com
As you mention in baselineProfile.managedDevices needs to specify which GMD to use. GMDs are created in android.testOptions.managedDevices.devices.
When selecting a managedDevices that does not exist in baselineProfile.managedDevices, the error thrown is about the task not found.
I'll improve the error message there but there are some reason for which we cannot change this behavior. Thanks for reporting this.
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit aeb2a56a1262140c803f87865cbb84551128a462
Author: Marcello Albano <maralb@google.com>
Date: Thu Dec 21 12:40:35 2023
Improved error message when specified managed device does not exist
Bug: 313803289
Test: n/a
Change-Id: Idea2b6d830807f215a576192bbbf844659a97c58
Relnote: Improved error message in baseline profile gradle plugin when specified managed device does not exist
M benchmark/baseline-profile-gradle-plugin/src/main/kotlin/androidx/baselineprofile/gradle/producer/BaselineProfileProducerPlugin.kt
M benchmark/baseline-profile-gradle-plugin/src/test/kotlin/androidx/baselineprofile/gradle/producer/BaselineProfileProducerPluginTest.kt
https://android-review.googlesource.com/2889227
Branch: androidx-main
commit aeb2a56a1262140c803f87865cbb84551128a462
Author: Marcello Albano <maralb@google.com>
Date: Thu Dec 21 12:40:35 2023
Improved error message when specified managed device does not exist
Bug: 313803289
Test: n/a
Change-Id: Idea2b6d830807f215a576192bbbf844659a97c58
Relnote: Improved error message in baseline profile gradle plugin when specified managed device does not exist
M benchmark/baseline-profile-gradle-plugin/src/main/kotlin/androidx/baselineprofile/gradle/producer/BaselineProfileProducerPlugin.kt
M benchmark/baseline-profile-gradle-plugin/src/test/kotlin/androidx/baselineprofile/gradle/producer/BaselineProfileProducerPluginTest.kt
ma...@google.com
pr...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.benchmark:benchmark-baseline-profile-gradle-plugin:1.3.0-alpha01
Description
STEPS TO REPRODUCE:
1. Use the IDE to auto-generate a baseline profile module
2. Change _ONE_ of the two device references from pixel6 to pixel8, but not both (ie: we would expect an error message, but not this error message)
3. run `./gradlew tasks` and notice that it says it can not determine the test task. This leads devs down a rabbit hole trying to solve the wrong thing. Ideally, it would tell them there is a device mismatch.
Issue is coming from: BaselineProfileProducerPlugin.kt#createTasksForVariant
(I was not able to place this ticket in the correct component)
```
* What went wrong:
A problem occurred configuring project ':baselineprofile'.
> com.android.build.gradle.internal.crash.ExternalApiUsageException: org.gradle.api.GradleException: It wasn't possible to determine the test task for managed device `pixel8Api34`.
Please check the managed devices specified in the baseline profile
configuration.
```
Studio Build: Iguana 2023.2.1 Canary 15
Version of Gradle Plugin: 8.2.0-rc03
Version of Gradle: 8.3-rc-2-all
Version of Java: 17
OS: Ubuntu 22.04.3 LTS x86_64