android / performance-samples

Samples to show APIs and best practices in Performance on Android

Home Page:https://d.android.com/topic/performance/overview

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

MacrobenchmarkSample doesn't run with Android Studio Electric Eel

yschimke opened this issue · comments

Trying to run a macrobenchmark test from the editor.

image

Works with Dolphin

Using

Android Studio Electric Eel | 2022.1.1 Canary 10
Build #AI-221.6008.13.2211.8963757, built on August 18, 2022
Runtime version: 11.0.15+0-b2043.56-8887301 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 5.17.11-1rodete2-amd64
GC: G1 Young Generation, G1 Old Generation
Memory: 3072M
Cores: 12
Registry:
    external.system.auto.import.disabled=true
    ide.text.editor.with.preview.show.floating.toolbar=false
    ide.images.show.chessboard=true

Non-Bundled Plugins:
    wu.seal.tool.jsontokotlin (3.7.4)
    idea.plugin.protoeditor (221.6008.13)
    de.ehmkah.projects.imgdiff (1.11.0)
    com.developerphil.adbidea (1.6.6)

Current Desktop: GNOME

I can't verify this on EE with the latest changes on main. Please verify if this problem still exists.

I've got Flamingo now, but same issue still happening.

Curiously, in the launcher, an "Android App" shows "macrobenchmark.app.main" but no androidTest modules.
"Android Instrumented Tests" shows only androidTest modules, and macrobenchmark doesn't have one.

I wonder if it's that?

I got the same problem. in the list of modules I cant find anymore the benchmark module so I cant start the test from AS EE

I can reproduce this issue now. It's not an issue with the code sample but appears to be a problem with Android Studio.
Please file an issue against Android Studio and link it here so we can follow up.

You can use the gutter icon (>>) to run the benchmarks in the meantime.
Screen Shot 2022-10-07 at 11 45 30

Also, running benchmarks directly from Gradle is not impacted by this problem.

Gutter icon doesn't work for me, but I'll raise an Android Studio bug.

Android Studio stopped selecting the proper build type.
As a workaround until the issue is solved, you can open the Build Variants and select the benchmark build type for the :app module and then run the tests as usual.