Status Update
No update yet.
Comments
ra...@google.com
The traces that are generated are correctly being parsed by
Attached is an example trace.
cc...@google.com
That file works for me as well, something is different about the ones I captured (likely device on which it was captured). Filed
@Leland - you should be able to workaround not getting usable macro traces by either trying a different device/OS image, or viewing the traces in
ra...@google.com
Reassigning to the default assignee given it looks like a Studio issue. Will wait for activity on the blocking bug.
bu...@google.com
Bugjuggler:
bu...@google.com
cc...@google.com
As discused in
Working on a fix.
ap...@google.com
Branch: androidx-main
commit 8f2ba6a5469f67b7e385878d704f97bde22419ce
Author: Chris Craik <ccraik@google.com>
Date: Mon Apr 08 14:49:54 2024
Fix macrobench method tracing flush on slower devices
Fixes: 329904950
Test: Enabled method tracing in SmallListStartupBenchmark
Relnote: "Fixed method traces flush in macrobench, so that method
traces are complete even on slower devices."
Change-Id: I6349a48dca4116ac9b481882395ee630785f6181
M benchmark/benchmark-common/src/main/java/androidx/benchmark/Shell.kt
M benchmark/benchmark-macro/src/main/java/androidx/benchmark/macro/MacrobenchmarkScope.kt
na...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.benchmark:benchmark-common:1.3.0-alpha03androidx.benchmark:benchmark-macro:1.3.0-alpha03
Description
Tried enabling method tracing in SmallListStartupBenchmark, and the resulting trace couldn't be opened by Studio.