[GRADLE-2835] Concurrent Gradle runs intermittently fail Created: 11/Jul/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1


Gradle is still awesome: I have a large, multi-project build with several dozen applications and services. I've defined run targets using Gradle's application plugin. This is great, because it lets developers use "gradle run" from an application's directory to run just that application with all the correct arguments and system properties.

Some of these applications depend on services provided by others, so I need to be able to run several applications at once. I can open two terminal windows in two different sub-project directories and type "gradle run" in each window to run both applications simultaneously. Sometimes that works; other times, I get this error:

A problem occurred configuring project ':sw:java:apps:foo'.
> Could not open buildscript class cache for build file '/workspace/blah/sw/java/apps/foo/build.gradle' (/home/me/.gradle/caches/1.7-rc-1/scripts/build_onimlior3lcqq5bugng0kgjb4/ProjectScript/buildscript).
> Timeout waiting to lock buildscript class cache for build file '/workspace/blah/sw/java/apps/foo/build.gradle' (/home/me/.gradle/caches/1.7-rc-1/scripts/build_onimlior3lcqq5bugng0kgjb4/ProjectScript/buildscript). It is currently in use by another Gradle instance.
Owner PID: unknown
Our PID: 3209
Owner Operation: unknown
Our operation:
Lock file: /home/me/.gradle/caches/1.7-rc-1/scripts/build_onimlior3lcqq5bugng0kgjb4/ProjectScript/buildscript/cache.properties.lock

Comment by Adam Murdoch [ 16/Jul/13 ]

You might be running into GRADLE-2795, when you edit the build script while `gradle run` is running.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:32:48 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.