It seems something about the tests for this project are chewing up too much memory on CircleCI.
This causes an intermittent build failure, which is something that Just Should Not Happen.
It may require something as simple as lowering maven's heap size, or further investigation. I suspect CircleCI will be having problems if the build process uses up a lot of memory on top of the spawned containers (of which some will be fairly demanding).
CircleCI failure output excerpt:
PID RSS %CPU COMMAND
15970 4318068 67.0 /usr/lib/jvm/jdk1.8.0/jre/bin/java -jar /home/ubuntu/testcontainers-java/modules/postgresql/target/surefire/surefirebooter261774409861515682.jar /home/ubuntu/testcontainers-java/modules/postgresql/target/surefire/surefire8554852648513290392tmp /home/ubuntu/testcontainers-java/modules/postgresql/target/surefire/surefire_2716773776951416696tmp
12388 395452 10.7 /usr/lib/jvm/jdk1.8.0/bin/java -Xmx512m -classpath /home/ubuntu/.m2/apache-maven-3.2.5/boot/plexus-classworlds-2.5.2.jar -Dclassworlds.conf=/home/ubuntu/.m2/apache-maven-3.2.5/bin/m2.conf -Dmaven.home=/home/ubuntu/.m2/apache-maven-3.2.5 org.codehaus.plexus.classworlds.launcher.Launcher integration-test
It seems something about the tests for this project are chewing up too much memory on CircleCI.
This causes an intermittent build failure, which is something that Just Should Not Happen.
It may require something as simple as lowering maven's heap size, or further investigation. I suspect CircleCI will be having problems if the build process uses up a lot of memory on top of the spawned containers (of which some will be fairly demanding).
CircleCI failure output excerpt: