Fixed
Status Update
Comments
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
Description
Version used: 1.1.0-alpha12
Devices/Android versions reproduced on: Pixel 6 (API 31), Pixel 3 (API 31), Emulator (API 27)
When running micro benchmarks with profiling set (e.g
StackSampling
), no traces are actually produced.It almost looks like the profiling isn't started at all?
I was checking the source code and it should print this message
Benchmark: Profiling output file: ...
which it doesn't.When the same tested on 1.1.0-alpha11, it works, creates the trace (and prints the output).