On 02/08/2013, at 10:02 PM, Szczepan Faber <szczepan.fa...@gradleware.com> wrote:
> It's not. We'd rather fix the problem differently than by exposing the > timeouts. +1. The locks are only supposed to be held for short periods of time, and the timeout is pretty generous. One cause of the timeout may be that the locking in dependency resolution is still fairly coarse-grained, in which case the solution is to make the locking finer-grained. We also want to do this to make parallel mode more efficient. Or the timeout might be due to some problem in the cache contention handling, in which case the solution is to fix the problem. For example, the cache locking is not particularly fair and may be starving one of the processes. Or the notification may be going missing. > > > On Fri, Aug 2, 2013 at 11:46 AM, Luke Daley <luke.da...@gradleware.com> wrote: > Is this timeout configurable? > > Begin forwarded message: > > > From: Gradle <noreply.gra...@getsatisfaction.com> > > Subject: New problem: Timeout waiting to lock artifact cache > > Date: 1 August 2013 8:28:06 PM GMT+01:00 > > To: luke.da...@gradleware.com > > > > Gradle > > swpalmer just reported this problem in Gradle: > > Timeout waiting to lock artifact cache > > > > 1.7.-rc-2 > > > > A problem occurred evaluating root project 'MyProject'. > > Could not resolve all dependencies for configuration ':nativesdk'. > > Timeout waiting to lock artifact cache > > (C:\Users\me\.gradle\caches\artifacts-26). It is currently in use by > > another Gradle instance. > > > > I get the above sometimes when doing many builds on the same machine. > > Is there a way to increase the timeout or something? > > Notify me when people reply REPLY > > This message sent from the Gradle community on Get Satisfaction. > > To unsubscribe or change your email settings, click here. Don't reply > > directly to this email. > > > > Create a customer community for your company at GetSatisfaction.com. > > > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > -- > Szczepan Faber > Principal engineer@gradleware; Lead@mockito -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
