You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have migrated to androidx.benchmark:benchmark-macro-junit4:1.2.2 and when running the assembleDebugAndroidTest task for firebase testlab I am getting the following error (Same for 1.2.0-1.2.2):
The same thing happens when the MacrobenchmarkSample app. In both cases adding: tools:overrideLibrary="androidx.benchmark.macro,androidx.benchmark.macro.junit4"
didn't help.
My workaround was to import the macro benchmark to implementation/api configurations instead of AndroidTest but the result is that when I build an apk or a bundle it generates huge traces in the assets folder named: trace_processor_shell_xxx' and trace box_xxx`, increasing the file by over 10MB.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi,
I have migrated to
androidx.benchmark:benchmark-macro-junit4:1.2.2
and when running the assembleDebugAndroidTest task for firebase testlab I am getting the following error (Same for 1.2.0-1.2.2):The same thing happens when the MacrobenchmarkSample app. In both cases adding:
tools:overrideLibrary="androidx.benchmark.macro,androidx.benchmark.macro.junit4"
didn't help.
My workaround was to import the macro benchmark to implementation/api configurations instead of AndroidTest but the result is that when I build an
apk
or abundle
it generates huge traces in the assets folder named:trace_processor_shell_xxx' and
trace box_xxx`, increasing the file by over 10MB.Thanks!
The text was updated successfully, but these errors were encountered: