Vojtech Hrdina
08/27/2021, 4:10 PM./gradlew :app:compileDebugUnitTestKotlin --debug
and it always stuck with following message
2021-08-27T16:31:11.764+0100 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
2021-08-27T16:31:11.764+0100 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
2021-08-27T16:31:11.764+0100 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
2021-08-27T16:31:11.764+0100 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
2021-08-27T16:31:11.764+0100 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
2021-08-27T16:31:11.764+0100 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
I already identified test file which causing this issue but I don’t know what could be wrong and it is stuck forever.
AGP 4.2.0
Kotlin 1.5.0
Gradle wrapper 6.8.3
Java 11
macOS 11.5.2, Ubuntu 16.04
org.gradle.jvmargs=-Xmx4608M -XX:MaxPermSize=1024m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8
org.gradle.parallel=true
org.gradle.caching=true
android.enableD8=true
android.useAndroidX=true
android.enableJetifier=true
kapt.use.worker.api=true
kapt.incremental.apt=true
kapt.include.compile.classpath=false
android.databinding.incremental=true
android.forceJacocoOutOfProcess=true
dmitriy.novozhilov
08/30/2021, 7:19 AM./gradlew -Dorg.gradle.debug=true -Dkotlin.compiler.execution.strategy="in-process" <task-to-exectute>
After that you can attach remote debugger to port 5005
dmitriy.novozhilov
08/30/2021, 7:21 AM./gradlew -Dkotlin.daemon.jvm.options="-agentlib:jdwp=transport=dt_socket\\,server=y\\,suspend=n\\,address=5005" <task-to-execute>
All further invocations should be used without -Dkotlin.daemon.jvm.options
(because daemon with opened port already started)