Started by an SCM change145233d37ee88eb2ac33029325167950cb1c159f128233d37ee88eb2ac33029325167950cb1c159f128refs/remotes/origin/master233d37ee88eb2ac33029325167950cb1c159f128233d37ee88eb2ac33029325167950cb1c159f128refs/remotes/origin/master233d37ee88eb2ac33029325167950cb1c159f128233d37ee88eb2ac33029325167950cb1c159f128refs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#145449255update-osmo-ci-on-slaves-dp #145145falsefalse145339022SUCCESS1607538668392https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/145/build2-deb9build-ansible- ttcn3-gbproxy-test-fr/osmo-gbproxy.cfg233d37ee88eb2ac33029325167950cb1c159f1281607538531000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgttcn3-gbproxy-test-fr: Fix hdlcnet device names
In Change-Id I80de01c96185c60fe2de7a8ffa9daed2669658e1 we introduced
the wrong hdlcnetX device names. We must use each devoce only once,
rather than trying to use hdlcnet1..4 twice.
Change-Id: I56f75995fe94b46b0210de2a4f83e384b4e4ca4f
2020-12-09 19:28:51 +0100233d37ee88eb2ac33029325167950cb1c159f128ttcn3-gbproxy-test-fr: Fix hdlcnet device nameseditttcn3-gbproxy-test-fr/osmo-gbproxy.cfg
githttps://jenkins.osmocom.org/jenkins/user/laforgelaforge