Status Update
Comments
ra...@google.com <ra...@google.com> #2
ys...@google.com <ys...@google.com> #3
Are there ways to make a visible annotation in the timelines, from the test code?
A dot showing the point at which we took it?
Or should we look at log lines?
ra...@google.com <ra...@google.com> #4
I would just surround it with a trace
section to make things easy. We can also consider opening up the user space tracing API that Macro benchmarks use under the hood.
ys...@google.com <ys...@google.com>
ra...@google.com <ra...@google.com> #5
Re-opening this bug so we can consider an API that makes it easy to report test results via Macrobenchmarks.
ys...@google.com <ys...@google.com> #6
With
cc...@google.com <cc...@google.com> #7
It will only delete files at the beginning of runs. If you're trying to store files on device between runs, you'll already have problems due to the json file clobbering the old file for each run. Profiling/Perfetto traces are sort of coincidentally immune to this, because we have to give them unique names due to how Studio file linking works.
In general, we want persisting files from run to run to be a responsibility of the host, and we don't want to persist more data on the device run to run than gradle already does. I'll acknowledge that we don't help you out much there today though - AGP will similarly fully clear pulled test output files after each run.
Probably worth a separate bug.
ys...@google.com <ys...@google.com> #8
This might be a quirk of my currently interactive workflow. I'm in an exploratory phase for creating the macrobenchmark tests, or using it for evaluating various enabled options. I find managing an archive of trace files confusing. No objection from me.
Description
Version used: 1.2.0-alpha14
When testing variants of UIs, it would be great to be able to capture a screenshot for a macrobenchmark test. Useful for a few reasons
- understanding a failure if the ui automator can't interact at some point
- confirm the variant you are testing is as you expect
Ideally saving the screenshot with the same naming as the perfetto trace, and putting a visible trace marker in perfetto / logs.