Fixed
Status Update
Comments
jg...@google.com <jg...@google.com>
pa...@google.com <pa...@google.com>
pa...@google.com <pa...@google.com> #2
Are there any updates here?
pa...@google.com <pa...@google.com>
pa...@google.com <pa...@google.com>
pa...@google.com <pa...@google.com>
an...@google.com <an...@google.com> #4
I couldn't move the logging off thread but I was able to address an area of concern in the callstack:
com.google.protobuf.Descriptors$FileDescriptor.internalBuildGeneratedFileFrom(Descriptors.java)
com.android.build.gradle.internal.cxx.logging.CxxLogging.<clinit>(CxxLogging.java:82)
com.android.build.gradle.internal.cxx.logging.LoggingMessage.getDescriptor(LoggingMessage.java:110)
com.android.build.gradle.internal.cxx.logging.LoggingMessage.hashCode(LoggingMessage.java:489)
java.util.HashMap.hash(HashMap.java:340)
java.util.HashMap.containsKey(HashMap.java:592)
java.util.HashSet.contains(HashSet.java:204)
This logic was deduplicating messages (including chatty 'info' messages). This deduplication shouldn't be needed anymore so I removed it.
I don't know how the 80ms from comment#1 was gathered so I can't say how much it has improved logging, but it should help quite a bit. Let me know if you can still measure a performance issue. The next step would be to reduce the 'info' that's logged.
com.google.protobuf.Descriptors$FileDescriptor.internalBuildGeneratedFileFrom(Descriptors.java)
com.android.build.gradle.internal.cxx.logging.CxxLogging.<clinit>(CxxLogging.java:82)
com.android.build.gradle.internal.cxx.logging.LoggingMessage.getDescriptor(LoggingMessage.java:110)
com.android.build.gradle.internal.cxx.logging.LoggingMessage.hashCode(LoggingMessage.java:489)
java.util.HashMap.hash(HashMap.java:340)
java.util.HashMap.containsKey(HashMap.java:592)
java.util.HashSet.contains(HashSet.java:204)
This logic was deduplicating messages (including chatty 'info' messages). This deduplication shouldn't be needed anymore so I removed it.
I don't know how the 80ms from
Description
when I select RUN -> Record Expresso Test
A previously used emulator device is invoked, (no prompt to select a device) Android Studio goes into debug mode, as expected and the app is launched. But there is no "Record Your Test" window appearing. I click and go through various screens and click widgets for the app in the emulator, but there is no way to create assertions or stop the test without the Test Recording Window.
Quite simply the Record Expresso Test is not working as it should according to official Android Developer documentation.
Build: AI-231.9392.1.2311.10809438, 202309141648
AI-231.9392.1.2311.10809438, JRE 17.0.7+0-17.0.7b1000.6-10550314x64 JetBrains s.r.o., OS Mac OS X(x86_64) v13.5.2, screens 5120.0x2880.0; Retina
AS: Hedgehog | 2023.1.1 Beta 5
Kotlin plugin: 231-1.9.10-release-459-AS9392.1.2311.10809438
Android Gradle Plugin: 8.1.0
Gradle: 8.3
Gradle JDK: JetBrains Runtime version 17.0.7
NDK: from module: 26.0.10792818, from local.properties: (not specified), latest from SDK: 26.0.10792818
CMake: from local.properties: (not specified), latest from SDK: 3.22.1-g37088a8, from PATH: (not found)
Source: send_feedback_icon```