openliberty_microprofile_tck - container name openliberty-mp-tck-test already in use

[lumpfish]

An openj9 linux_x86-64 run of openliberty_microprofile_tck_0 on test-packet-ubuntu1604-x64-1 failed because the docker container name was already is use.
Job link: https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/333/console

Output text around point of failure:

15:11:59  ===============================================
15:11:59  Running test openliberty_microprofile_tck_0 ...
15:11:59  ===============================================
15:11:59  openliberty_microprofile_tck_0 Start Time: Mon Jun 29 14:11:59 2020 Epoch Time (ms): 1593439919134
15:11:59  "/home/jenkins/workspace/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/openjdkbinary/j2sdk-image/bin/java" -Xshareclasses:destroyAll; "/home/jenkins/workspace/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/openjdkbinary/j2sdk-image/bin/java" -Xshareclasses:groupAccess,destroyAll; echo "cache cleanup done";
15:11:59  JVMSHRC005I No shared class caches available
15:11:59  JVMSHRC005I No shared class caches available
15:11:59  cache cleanup done
15:11:59  variation: NoOptions
15:11:59  JVM_OPTIONS:  
15:11:59  { itercnt=1; \
15:11:59  mkdir -p "/home/jenkins/workspace/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/openjdk-tests/TKG/../TKG/test_output_15934399178863/openliberty_microprofile_tck_0"; \
15:11:59  cd "/home/jenkins/workspace/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/openjdk-tests/TKG/../TKG/test_output_15934399178863/openliberty_microprofile_tck_0"; \
15:11:59  /home/jenkins/workspace/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/openjdk-tests/TKG/../external/external.sh --run --tag nightly --version 8 --impl openj9 --dir openliberty-mp-tck --reportsrc /testResults/surefire-reports --reportdst "/home/jenkins/workspace/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/openjdk-tests/TKG/../TKG/test_output_15934399178863/openliberty_microprofile_tck_0" --docker_args "-v /home/jenkins/workspace/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/openjdkbinary/j2sdk-image:/opt/java/openjdk" ; \
15:11:59  	if [ $? -eq 0 ] ; then echo ""; echo "openliberty_microprofile_tck_0""_PASSED"; echo ""; cd /home/jenkins/workspace/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/openjdk-tests/TKG/..;  else echo ""; echo "openliberty_microprofile_tck_0""_FAILED"; echo ""; fi; \
15:11:59  	/home/jenkins/workspace/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/openjdk-tests/TKG/../external/external.sh --clean --tag nightly --version 8 --impl openj9 --dir openliberty-mp-tck; } 2>&1 | tee -a "/home/jenkins/workspace/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/openjdk-tests/TKG/../TKG/test_output_15934399178863/TestTargetResult";
15:11:59  docker run --rm -v /home/jenkins/workspace/Test_openjdk8_j9_sanity.external_x86-64_linux_openliberty-mp-tck/openjdkbinary/j2sdk-image:/opt/java/openjdk --name openliberty-mp-tck-test adoptopenjdk-openliberty-mp-tck-test:8-jdk-ubuntu-openj9-full 
15:11:59  docker: Error response from daemon: Conflict. The container name "/openliberty-mp-tck-test" is already in use by container "2b13e99f24957ed0e2cde7366ac5bfa79b28162ef37883ebeeb59c3862e3c625". You have to remove (or rename) that container to be able to reuse that name.
15:11:59  See 'docker run --help'.
15:11:59  
15:11:59  openliberty_microprofile_tck_0_FAILED

Can be rerun via https://ci.adoptopenjdk.net/job/Grinder/parambuild/?JDK_VERSION=8&JDK_IMPL=openj9&

[smlambert]

Full rerun link (one above is incomplete):
https://ci.adoptopenjdk.net/job/Grinder/parambuild/?JDK_VERSION=8&JDK_IMPL=openj9&BUILD_LIST=external/openliberty-mp-tck&PLATFORM=x86-64_linux&TARGET=openliberty_microprofile_tck_0

[smlambert]

This happens when the test gets aborted or can not otherwise clean up after itself. Plan is to augment TKG to do environment check before each run. Related: adoptium/TKG#45

[smlambert]

We have added a docker prune command to clean_image in #1890 which will run before each external test is run. This 'already in use' failure will now not be encountered, because existing images with same name will be pruned, to make sure we start on a clean slate when building and running docker based testing found in the external repo.