Sporadic Robolectric Test Failures When Running Inside Docker Container

I am trying to move our Android team onto a Cloud-based CI solution. Other departments within the company have completed this task and we have an Enterprise TeamCity License levera

Solution 1:

So, my own CircleCI 2.0 build started to fail with something similar after the solution graduated from beta and in diagnosing and correcting that build, it lead me to the answer for this. This is a memory issue. The container is running out of memory and not failing gracefully. There were a few other signals that this was the case and I had started playing with JAVA_OPTS/GRADLE_OPTS settings. In the end specifying explicitly not to use the daemon and controlling the number of JVM forks solved it;

--no-daemon--max-workers2

This thread has other permutations of the memory issues you will encounter with Docker + Java + Gradle + Android. A bit painful, but worth it.