Seeing traces cutting off too early, before e.g. startActivityAndWait have fully completed, which results in an exception like the following:

java.lang.IllegalStateException: Error, different metrics observed in different iterations.

Iteration 1 missing keys [startupMs]Please report a bug, and include a logcat capture, and all traces captured by this test run:
/storage/emulated/0/Android/media/androidx.benchmark.integration.macrobenchmark.test/TrivialStartupBenchmark_startup[startup=COLD,compilation=SpeedProfile[iterations=3]]_iter000_2021-07-15-22-21-37.trace
/storage/emulated/0/Android/media/androidx.benchmark.integration.macrobenchmark.test/TrivialStartupBenchmark_startup[startup=COLD,compilation=SpeedProfile[iterations=3]]_iter001_2021-07-15-22-21-41.trace
/storage/emulated/0/Android/media/androidx.benchmark.integration.macrobenchmark.test/TrivialStartupBenchmark_startup[startup=COLD,compilation=SpeedProfile[iterations=3]]_iter002_2021-07-15-22-21-44.trace
DeviceInfo(Brand=google, Model=Pixel 4a (5G), SDK=30, BuildFp=google/bramble/bramble:11/RQ3A.210605.003/7295351:userdebug/dev-keys)
...

See attached trace.

Seeing this in CI frequently with androidx.benchmark.integration.macrobenchmark.SmallListStartupBenchmark, e.g. https://android-build.googleplex.com/builds/tests/view?invocationId=I51900009972024845&redirect=http%3A%2F%2Fab%2FI51900009972024845&testClass=SmallListStartupBenchmark&testMethod=startup%5Bstartup%3DHOT%2Ccompilation%3DNone%5D&testPackage=androidx.benchmark.integration.macrobenchmark

This is likely due to switch either to am start (http://aosp/1751627), or reduction of sleep before killing the trace (http://aosp/1751631).

Issue 193827052

Mentioned issues (1)

Links (6)

Issue metadata