IssueTracker

Component used: andnroidx.benchmark:benchmark-macro

Version used: 1.1.0-alpha12

Devices/Android versions reproduced on: Pixel 3

When running measureRepeated with CompilationMode.None and any StartupMode other than COLD first runs measureBlock() and later setupBlock.

This shouldn't happen, because e.g. developers may want to interact with UI in setupBlock and expect some UI being present on the screen which can be later measured inside measureBlock.