Started by an SCM change00554564561.00592259225258c6ebc8c764fb4d7170372112649a87e3c440d838c6ebc8c764fb4d7170372112649a87e3c440d83refs/remotes/origin/master8c6ebc8c764fb4d7170372112649a87e3c440d838c6ebc8c764fb4d7170372112649a87e3c440d83refs/remotes/origin/master8c6ebc8c764fb4d7170372112649a87e3c440d838c6ebc8c764fb4d7170372112649a87e3c440d83refs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#525456255update-osmo-ci-on-slaves-dp #525525falsefalse5251449717SUCCESS1707477666830https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/525/build2-deb11build-ansible- ttcn3-bts-test/jenkins.sh8c6ebc8c764fb4d7170372112649a87e3c440d831707476556000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.dettcn3-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
2024-02-09 18:02:36 +07008c6ebc8c764fb4d7170372112649a87e3c440d83ttcn3-bts-test: do not start osmo-bts-virtual / virtphy containerseditttcn3-bts-test/jenkins.sh
githttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiy