IssueTracker

Can you attach logcat and traces from iterations where the metric wasn't captured?

Thanks very much for the logs!

Are you sure you're using benchmark 1.2.3?

In 1.2.0-alpha04 we removed the constraint to look for startActivityAndWait (see b/245414235), but it's still in your query/results. It's possible we had a branch management issue when releasing, but can you check the version of benchmark you're using?

On a newer version, the query results for this iteration look like they should work, I tried converting them to slices in the internal implementation of StartupTimingQuery:

    listOf(
        Slice("MetricsLogger:launchObserverNotifyIntentStarted",748393772361,29705),
        Slice("launching: androidx.benchmark.integration.macrobenchmark.target",748404581583,881311671),
        Slice("activityResume",748731008508,4916798),
        Slice("Choreographer#doFrame",748764833776,519637337),
        Slice("DrawFrame",748897201189,387112642),
        Slice("Choreographer#doFrame",749285086939,89017),
        Slice("Choreographer#doFrame",749305484396,730140),
        Slice("DrawFrame",749305899852,121651546),
    )

And received the following startup event:

SubMetrics(timeToInitialDisplayNs=879732248, timeToFullDisplayNs=null, timelineRangeNs=748404581583..749284313831)

So you should be good with new versions of macrobenchmark.

The other constraint we removed in that same fix was asserting that the launching event was contained in the startActivityAndWait event, which seems to be the problem in this iteration:

04-01 11:54:55.097  6289  6311 I System.out: query result line "startActivityAndWait",748335793781,1096645119
04-01 11:54:55.097  6289  6311 I System.out: query result line "launching: <app_test_package>",748404581583,881311671

748335793781 + 1096645119 is greater than 748404581583, so the launching: event starts after the startActivityAndWait slice from macrobenchmark. Not sure why that is without looking at a trace, but you could look to see if there's anything strange there (like startActivityAndWait not waiting for the actual launch somehow, that would do it).