Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Cache It is currently in use by another Gradle instance

I don't understand why this is happening.

Gradle sync failed: Timeout waiting to lock buildscript class cache for build file '/Users/user/Documents/android-studio-pubble/App/build.gradle' (/Users/user/.gradle/caches/2.2.1/scripts/build_bqh4uod6cat7u5cm5qkoye2ky/ProjectScript/buildscript). It is currently in use by another Gradle instance.
         Owner PID: unknown
         Our PID: 909
         Owner Operation: unknown
         Our operation: Initialize cache
         Lock file: /Users/user/.gradle/caches/2.2.1/scripts/build_bqh4uod6cat7u5cm5qkoye2ky/ProjectScript/buildscript/cache.properties.lock
         Consult IDE log for more details (Help | Show Log)

general gladle is:

// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
    repositories {
        jcenter()
        maven { url '/Users/user/Documents/sdk/extras/android/m2repository' }

    }
    dependencies {
        classpath 'com.android.tools.build:gradle:1.2.3'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        jcenter()
        mavenCentral()
    }
    tasks.withType(JavaCompile) {
        options.compilerArgs << "-Xlint:deprecation" << "-Xlint:unchecked"
    }
}

App gradle file is:

apply plugin: 'com.android.application'

android {
    signingConfigs {
        pubblemod {
            keyAlias 'testapp'
            keyPassword 'testapp'
            storeFile file('/Users/user/Documents/sdk/testapp.keystore')
            storePassword 'testapp'
        }
    }
    compileSdkVersion 22
    buildToolsVersion '22.0.1'
    defaultConfig {
        applicationId "com.test.app"
        minSdkVersion 16
        targetSdkVersion 22
        versionCode 1
        versionName "1.1.0"
        multiDexEnabled true
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
        debug {

        }
    }
    packagingOptions {
        exclude 'META-INF/DEPENDENCIES.txt'
        exclude 'META-INF/LICENSE.txt'
        exclude 'META-INF/NOTICE.txt'
        exclude 'META-INF/NOTICE'
        exclude 'META-INF/LICENSE'
        exclude 'META-INF/DEPENDENCIES'
        exclude 'META-INF/notice.txt'
        exclude 'META-INF/license.txt'
        exclude 'META-INF/dependencies.txt'
        exclude 'META-INF/LGPL2.1'
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_7
        targetCompatibility JavaVersion.VERSION_1_7
    }
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    compile 'com.intellij:annotations:+@jar'
    compile 'com.android.support:appcompat-v7:22.2.1'
    compile 'com.android.support:design:22.2.0'
    compile 'com.android.support:support-v13:22.0.+'
    compile 'org.apache.commons:commons-lang3:3.2.+'
    compile 'com.jakewharton:butterknife:6.0.0'
    compile 'com.afollestad:material-dialogs:0.7.7.0'
    compile 'it.neokree:MaterialTabs:0.11'
    compile 'com.github.johnkil.android-appmsg:appmsg:1.2.0'
    compile 'com.cocosw:bottomsheet:1.+@aar'
    compile 'de.psdev.licensesdialog:licensesdialog:1.7.0'
    compile 'com.afollestad:material-dialogs:0.7.7.0'
    compile 'joda-time:joda-time:2.7'

    compile 'com.google.android.gms:play-services:3.1+'
    compile project(':loadingLibrary')
    compile project(':welcomeLibrary')

//    compile project(':licenceDialogLibrary')
    compile project(':Bootstrap')
}

It used to work and then i wanted to add a new module and it all went downwards after that. Does anyone had this problem and solved it? I don't even know what is wrong..or how i made this.

like image 561
Gabriela Radu Avatar asked Aug 17 '15 20:08

Gabriela Radu


People also ask

What is the use case for Gradle cache lock?

Sorry, something went wrong. Another use case is when a user runs multiple different builds of different projects on multiple different hosts, all using his/her account. This is typical of environments with network mounted home directories. Gradle has to pro-actively release the lock as soon as it is done with the cache.

What is the difference between local and global Gradle cache?

Just a minor piece of terminology: The .gradle directory inside your project is the local cache. The global caches are in the user home by default. Sorry, something went wrong.

Can you have concurrent writes in Gradle remote cache?

It's at your own risk, basically: you can have concurrent writes. Sorry, something went wrong. Would be nice if Gradle supported the same as it works perfectly well for maven. Gradle Remote Cache is much slower than disk cache. Keeping an additional read only cache adds quite some complexity.

Why do all my Gradle jobs keep crashing?

The jobs share the same Gradle cache. Even though no dependencies have been changed, the first build locks the cache. Subsequent builds now wait, and ultimately time out. This causes spurious build failures. Basically the kind of thing we shouldn't have to suffer when using a tool which alleges to make development life better.


1 Answers

The easiest way to solve this is to be delete a cache.

For Windows it's under C:\Users\Administrator\.gradle\caches

For Mac OSX it's ~/.gradle/caches

Try to execute the following command:

find ~/.gradle -type f -name "*.lock" | while read f; do rm $f; done
like image 69
Bogdan Ustyak Avatar answered Sep 20 '22 19:09

Bogdan Ustyak