IssueTracker

Saw this as well on Mokey running recent tot master build.

First benchmark only shows jit happening during the allocation phase

Benchmark in the middle of the suite shows it happening during measurement as well, before method tracing and allocation counting.

I verified during the run that the platform still considers the app compiled:

> adb shell dumpsys package dexopt | grep -A1 androidx.compose.ui.benchmark.test
  [androidx.compose.ui.benchmark.test]
    path: /data/app/~~E9h-5MtFh1GXjXCq3kQo8g==/androidx.compose.ui.benchmark.test-jOZKJEy6zBL_SpFBJqlisA==/base.apk
      arm64: [status=speed] [reason=cmdline] [primary-abi]
        [location is /data/app/~~E9h-5MtFh1GXjXCq3kQo8g==/androidx.compose.ui.benchmark.test-jOZKJEy6zBL_SpFBJqlisA==/oat/arm64/base.odex]

Disabling method tracing works around this issue, but we don't seem to see it in CI, on older platform versions (wembley 30, sargo 31): https://screenshot.googleplex.com/57EEmDd8MBNvdwE

My guess is that when turning off method tracing, something fails to be cleaned up, and we don't get to keep using the odex/art files from the speed compilation.