[2.12] Locking issue


(Hristo Stoyanov) #1

Hello,
I am getting the below issue when I have two gradle processes. I am not sure why Gradle uses exclusive locks like that. The issue only shows sometimes, it is rather inconsistent. Any idea?

  • What went wrong:
    A problem occurred configuring root project ‘trowelo’.

Could not open cp_proj class cache for build file ‘/projects/trowelo/build.gradle’ (/root/.gradle/caches/2.12/scripts/build_8mzlztp9cyvnrl2h8y19j4doc/cp_proj).
Timeout waiting to lock cp_proj class cache for build file ‘/projects/trowelo/build.gradle’ (/root/.gradle/caches/2.12/scripts/build_8mzlztp9cyvnrl2h8y19j4doc/cp_proj). It is currently in use by another Gradle instance.
Owner PID: unknown
Our PID: 10263
Owner Operation: unknown
Our operation: Initialize cache
Lock file: /root/.gradle/caches/2.12/scripts/build_8mzlztp9cyvnrl2h8y19j4doc/cp_proj/cache.properties.lock

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

(René Groeschke) #2

Is that something that you only see with Gradle 2.12 or have you experienced this with former Gradle versions too?