Started by an SCM change00553963961.008457845742746e4362ae261296b35f8278bf90ab839360f39f246e4362ae261296b35f8278bf90ab839360f39f2refs/remotes/origin/master46e4362ae261296b35f8278bf90ab839360f39f246e4362ae261296b35f8278bf90ab839360f39f2refs/remotes/origin/master46e4362ae261296b35f8278bf90ab839360f39f246e4362ae261296b35f8278bf90ab839360f39f2refs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#427396255update-osmo-ci-on-slaves-dp #427427falsefalse427986117SUCCESS1675085469037https://jenkins.osmocom.org/jenkins/view/SDR/job/update-osmo-ci-on-slaves-dp/427/build2-deb11build-ansiblettcn3-ns-test/jenkins-fr.shjenkins-common.shttcn3-gbproxy-test-fr/jenkins.shttcn3-fr-test/jenkins.sh46e4362ae261296b35f8278bf90ab839360f39f21675082730000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deFR testsuites: clean up all networks before start Add a new network_clean_remove_all_ttcn3 function and use it in the fr related testsuites to ensure no network is running before the test starts. We just had the situation where the network link between gtp0-deb10fr (where these testsuites run exclusively, and only one at a time) and the jenkins host went down. And so the clean up trap apparently did not run and starting a new test fails as the old network still exists and has the network devices attached. Related: OS#5802 Change-Id: I6a9464a11edcba978be08764bec9de19760a5c77 2023-01-30 13:45:30 +010046e4362ae261296b35f8278bf90ab839360f39f2FR testsuites: clean up all networks before starteditttcn3-fr-test/jenkins.sheditttcn3-gbproxy-test-fr/jenkins.sheditjenkins-common.sheditttcn3-ns-test/jenkins-fr.shgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith