Fixed
Status Update
Comments
cc...@google.com <cc...@google.com>
ap...@google.com <ap...@google.com> #2
Project: platform/frameworks/support
Branch: androidx-main
commit 5888d75c39e128d4762c21acdc8aa7a7deb7226e
Author: Omar Ismail <omarismail@google.com>
Date: Fri Jul 12 15:42:55 2024
Remove js target from testutils as it's not ready yet
BUG: 352722444
Change-Id: I2d31d1539f1b72212e9f1a3befe39546b3aadbe0
M testutils/testutils-ktx/build.gradle
https://android-review.googlesource.com/3170300
Branch: androidx-main
commit 5888d75c39e128d4762c21acdc8aa7a7deb7226e
Author: Omar Ismail <omarismail@google.com>
Date: Fri Jul 12 15:42:55 2024
Remove js target from testutils as it's not ready yet
BUG: 352722444
Change-Id: I2d31d1539f1b72212e9f1a3befe39546b3aadbe0
M testutils/testutils-ktx/build.gradle
pr...@google.com <pr...@google.com> #3
Project: platform/frameworks/support
Branch: androidx-main
commit fb644fcb5ba87a19f3b3ab3cfeea60678643ffa0
Author: Omar Ismail <omarismail@google.com>
Date: Fri Jul 12 14:44:38 2024
Update importMaven to include wasmJs targets and klib files
BUG: 352722444
TESTED: Ran import maven on kotlin stdlib and it downloaded the wasm targets as well
Change-Id: Ic0dced9e209db4846ceef1527dc6b06c061581da
M development/importMaven/src/main/kotlin/androidx/build/importMaven/ArtifactResolver.kt
M development/importMaven/src/main/kotlin/androidx/build/importMaven/CustomMetadataRules.kt
https://android-review.googlesource.com/3169102
Branch: androidx-main
commit fb644fcb5ba87a19f3b3ab3cfeea60678643ffa0
Author: Omar Ismail <omarismail@google.com>
Date: Fri Jul 12 14:44:38 2024
Update importMaven to include wasmJs targets and klib files
BUG: 352722444
TESTED: Ran import maven on kotlin stdlib and it downloaded the wasm targets as well
Change-Id: Ic0dced9e209db4846ceef1527dc6b06c061581da
M development/importMaven/src/main/kotlin/androidx/build/importMaven/ArtifactResolver.kt
M development/importMaven/src/main/kotlin/androidx/build/importMaven/CustomMetadataRules.kt
Description
Component used: Macrobenchmark 1.3.0-alpha05
It's not possible to use the new
perfettoConfig
parameter unless adding additionalbenchmark-common
dependency.This is not intuitive as users don't really know where it's coming from unless digging into cs.android.com.
Is it possible to make it automatically available?
I don't know if it's reasonable to make the
benchmark-common
defined asapi
? Or if it's possible to only expose thePerfettoConfig
from that module?If none of this is feasible, can we at least update the
kDoc
to warng about the need to include this dependency?