ModuleVersionResolveException (waggling) [gradle 1.6]

From time to time gradle throws a ModuleVersionResolveException from time to time (like 1 in 20 builds).

This happens in an CI environment (~ 15 build machines) using an Ivy repository. Using debug output I only see gradle errors, but no errors from ivy itself (ivy loggin is functional since I see the startup info stuff with org.gradle.api.internal.artifacts.ivyservice.IvyLoggingAdaper). The artifacts are in the repo and have not changed.

Any idea how to find the problem and how to solve it ?

Cause 1: org.gradle.api.internal.artifacts.ivyservice.ModuleVersionResolveException: Could not resolve org.jboss.arquillian.extension:arquillian-drone-impl:1.2.0.Alpha2.
Required by:
 at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.UserResolverChain.resolve(
 at org.gradle.api.internal.artifacts.ivyservice.clientmodule.ClientModuleResolver.resolve(
 at org.gradle.api.internal.artifacts.ivyservice.projectmodule.ProjectDependencyResolver.resolve(
 at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.LazyDependencyToModuleResolver$AbstractVersionResolveResult.resolve(
 at org.gradle.api.internal.artifacts.ivyservice.resolveengine.DependencyGraphBuilder$ModuleVersionSelectorResolveState.resolve(
 at org.gradle.api.internal.artifacts.ivyservice.resolveengine.DependencyGraphBuilder$DefaultModuleRevisionResolveState.getMetaData(
 at org.gradle.api.internal.artifacts.ivyservice.resolveengine.DependencyGraphBuilder$DependencyEdge.calculateTargetConfigurations(
 at org.gradle.api.internal.artifacts.ivyservice.resolveengine.DependencyGraphBuilder$DependencyEdge.attachToTargetConfigurations(
 at org.gradle.api.internal.artifacts.ivyservice.resolveengine.DependencyGraphBuilder.traverseGraph(
 at org.gradle.api.internal.artifacts.ivyservice.resolveengine.DependencyGraphBuilder.resolve(
 at org.gradle.api.internal.artifacts.ivyservice.resolveengine.DefaultDependencyResolver.resolve(
 at org.gradle.api.internal.artifacts.ivyservice.CacheLockingArtifactDependencyResolver$1.create(
 at org.gradle.api.internal.artifacts.ivyservice.CacheLockingArtifactDependencyResolver$1.create(
 at org.gradle.cache.internal.DefaultCacheAccess.useCache(
 at org.gradle.cache.internal.DefaultPersistentDirectoryStore.useCache(

Is it possible that there’s a network glitch here?

Does it work the very next build?

Currently I have added --refresh-dependencies when building on CI, which workarounds the problem. So I don’t think the network is the problem here. I also don’t see any ivy-resolve warnings or errors in the debug log. I checked the gradle cache on one machine after one such failure and the failing module wasn’t in the cache and the build log showed now ivy stuff to fetch it.

I haven’t observed a build failure on the next run on the next machine.

I’ve uploaded the complete failure message to

Currently I have added --refresh-dependencies when building on CI, which workarounds the problem. So I don’t think the network is the problem here.

I don’t understand. So when you run with --refresh-dependencies you never see the problem?

Can you run with ‘–info’ please. It will show the network traffic information.

Exactly, --refresh-dependencies never showed this failure.

With --info I don’t see any related messages in the build log (I can send you the full info or debug log by email if you like).

Send the full info log for a failure to luke.daley at please.