From 8c6ebc8c764fb4d7170372112649a87e3c440d83 Mon Sep 17 00:00:00 2001 From: Vadim Yanitskiy Date: Fri, 9 Feb 2024 17:39:54 +0700 Subject: [PATCH] ttcn3-bts-test: do not start osmo-bts-virtual / virtphy containers We cannot execute the virtphy based testcases due to the limitations of Docker (see https://github.com/moby/libnetwork/issues/2397). The function starting the testsuite was already commented out, but not the lines starting containers with osmo-bts-virtual and virtphy. To put it simple, we start and immediately terminate those containers. And since recently (Feb 1st), we started seeing socket creation errors in both containers, causing jenkins.sh to abort early. It's yet unclear what's the cause of those socket errors, but regardless of that we should still be running other pending testcases. Change-Id: I7c9ccc9cc400edb7a05e222e51671fd49631a4cd Fixes: OS#6352 --- ttcn3-bts-test/jenkins.sh | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/ttcn3-bts-test/jenkins.sh b/ttcn3-bts-test/jenkins.sh index 4128e081..92d83ef1 100755 --- a/ttcn3-bts-test/jenkins.sh +++ b/ttcn3-bts-test/jenkins.sh @@ -182,8 +182,11 @@ docker_kill_wait ${BUILD_TAG}-fake_trx docker_kill_wait ${BUILD_TAG}-bts cp virtphy/osmo-bts.gen.cfg $VOL_BASE_DIR/bts/ network_replace_subnet_in_configs -start_bts virtual 0 -start_virtphy +# FIXME: multicast to/from a docker bridge network is currently not possible. +# See https://github.com/moby/libnetwork/issues/2397. +echo "XXX: not running the virtphy configuration" +#start_bts virtual 0 +#start_virtphy # ... and execute the testsuite again with different cfg #start_testsuite virtphy