osmocom
/
docker-playground
mirror of https://gerrit.osmocom.org/docker-playground
10
0
Fork 0
Code Releases Activity

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
This commit is contained in:
Vadim Yanitskiy 2024-02-09 17:39:54 +07:00
parent 27a8a92deb
commit 8c6ebc8c76
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
ttcn3-bts-test/jenkins.sh
View File

@ -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