We weren't able to run out build against 1.9-rc-1 because of the transitive dependency resolve issue.
Here's our stack trace: https://gist.github.com/johnrengelman/7249347 I should point out that on our CI server we can be running concurrent builds. So this could be related to two builds trying to access that store at the same time. I suppose I could work around the problem by moving the Gradle cache into a unique location for each build thread. However, since this hasn't been an issue before, I figure it is a regression. -- John Engelman On Thursday, October 31, 2013 at 2:07 AM, Szczepan Faber-2 [via Gradle] wrote: > Hey, > > Did you encounter similar issues with 1.9-rc-1? Can you submit a stack trace > (gist, etc.) > > Thanks for reporting! > > > On Thu, Oct 31, 2013 at 4:01 AM, johnrengelman <[hidden email] > (/user/SendEmail.jtp?type=node&node=5711965&i=0)> wrote: > > I've been running our build in the 1.9-rc-2 to check things out and we've > > been getting intermittent failures on our build server with this error: > > > > Caused by: java.lang.IllegalStateException: Cannot start long running > > operation, as the artifact cache (/mnt/jenkins/.gradle/caches/modules-2) has > > not been locked. > > > > This is the root exception which bubbles up as a "cannot resolve all > > dependencies". > > > > I haven't been able to isolate any particular scenario that causes the > > error, but a subsequent restart of the job runs the build successfully. > > > > I know there were some significant changes around the file and artifact > > cache structure for 1.9, so I figured I should get this out there. > > > > > > > > -- > > View this message in context: > > http://gradle.1045684.n5.nabble.com/Artifact-cache-locking-issues-in-1-9-rc-2-tp5711964.html > > Sent from the gradle-dev mailing list archive at Nabble.com > > (http://Nabble.com). > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > > > -- > Szczepan Faber > Principal engineer@gradle; Founder@mockito > Join me at the Gradle eXchange 2013, Oct 28th in London: > http://skillsmatter.com/event/java-jee/gradle-exchange-2013 > > > > If you reply to this email, your message will be added to the discussion > below: > http://gradle.1045684.n5.nabble.com/Artifact-cache-locking-issues-in-1-9-rc-2-tp5711964p5711965.html > > To start a new topic under gradle-dev, email > ml-node+s1045684n1436218...@n5.nabble.com > (mailto:ml-node+s1045684n1436218...@n5.nabble.com) > To unsubscribe from gradle-dev, click here > (http://gradle.1045684.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1436218&code=am9obi5yLmVuZ2VsbWFuQGdtYWlsLmNvbXwxNDM2MjE4fDIyMTUyNjEzNQ==). > NAML > (http://gradle.1045684.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml) > -- View this message in context: http://gradle.1045684.n5.nabble.com/Artifact-cache-locking-issues-in-1-9-rc-2-tp5711964p5711972.html Sent from the gradle-dev mailing list archive at Nabble.com.
