IssueTracker

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?

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.

Re-opening this bug so we can consider an API that makes it easy to report test results via Macrobenchmarks.

With https://android-review.googlesource.com/2576990 it will start deleting files, might be good to think about how to save the files in some automated ways. I'll suspect you might see a non-zero number of lost test runs for users.

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.

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.