Good evening, I have upgraded our multiplatform pr...
# gradleo
Ola Adolfsson
08/22/2020, 5:21 PMGood evening, I have upgraded our multiplatform project from 1.3.72 to 1.4 following the migration guide on kotlinglang. Everything went pretty smooth except that for one project/module where the task ompileKotlinJshangs without any errors or warning. There is no particular difference between the modules and I have no ideas left. Is there a way to debug the gradle task in order to understand what´s happening?
d
dwursteisen
08/23/2020, 7:44 AMYes it is. You can run the task in intellij in debug mode.
After it can be more tricky if the task is running something in a forked VM.
First maybe you can just run the task with --info passed to gradle (or --debug but it might be too verbose)
o
Ola Adolfsson
08/23/2020, 5:43 PMThanks for the help. The gradle deamon timeout while requesting a new resource
Ola Adolfsson
08/23/2020, 5:43 PM2020-08-23T19:41:07.912+0200 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.2020-08-23T19:41:17.910+0200 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.2020-08-23T19:41:17.910+0200 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.2020-08-23T19:41:17.910+0200 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.2020-08-23T19:41:17.910+0200 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.2020-08-23T19:41:17.910+0200 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.2020-08-23T19:41:17.910+0200 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.Ola Adolfsson
08/23/2020, 5:53 PMAnd here is a part of the jstack
8 Views