When launching my test suite from the command line:

./gradlew "connectedDebugAndroidTest"

there is a task that is taking more than 4 minutes, even if no changes have been made:

> :app:processDebugAndroidTestManifest > Resolve dependencies of :app:debugAndroidTestRuntimeClasspath > espresso-core-$project.espressoVersion.pom

It only takes 20 seconds to run the entire test suite, and maybe 10 seconds to compile. During this 4-minute task, there is only one java process on the machine, and it is consuming less than 0.01% cpu (according to top).

Is this task necessary? It doesn't appear to be doing anything. Is there a way to simply remove it from the build, or skip it?

When launching my test suite from the command line:

./gradlew "connectedDebugAndroidTest"

there is a task that is taking more than 4 minutes, even if no changes have been made:

> :app:processDebugAndroidTestManifest > Resolve dependencies of :app:debugAndroidTestRuntimeClasspath > espresso-core-$project.espressoVersion.pom

It only takes 20 seconds to run the entire test suite, and maybe 10 seconds to compile. During this 4-minute task, there is only one java process on the machine, and it is consuming less than 0.01% cpu (according to top).

Is this task necessary? It doesn't appear to be doing anything. Is there a way to simply remove it from the build, or skip it?

• android
• gradle

Share Improve this question Follow edited Jan 11 at 12:49 Andrew T. 4,70788 gold badges4646 silver badges6868 bronze badges asked Jan 11 at 11:31 Byron HawkinsByron Hawkins 2,70522 gold badges2828 silver badges3636 bronze badges 2

• 1 If you are using Espresso, Gradle needs Espresso and its dependencies. Since that task does not normally take minutes, you might want to investigate further for why it is taking Gradle that long. For example, perhaps there is a networking issue that is causing abnormally long response times when looking up artifacts in some specific Maven repository. – CommonsWare Commented Jan 11 at 13:42
• @CommonsWare that fixed it. My development machine has problems with the wifi, but if I share my phone's internet over usb, suddenly that task takes much less than a second. Seems like kind of an extreme timeout setting though. – Byron Hawkins Commented Jan 11 at 14:27

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 1

Gradle wants to check on the status of dependencies on each build by default. Your specific line is for Espresso, which (presumably) you are using in your tests.

Since you are using ./gradlew, you could try adding --offline to your command to tell Gradle to always work purely from cache. If you add dependencies or change dependency versions, though, you will need to run at least once without that switch.

You could also try playing with Gradle timeout settings, though usually that's a solution for increasing the timeout rather than decreasing it.