Started by an SCM change159096f6a0030aa5a384df7466b4b0fc7506fc4611b096f6a0030aa5a384df7466b4b0fc7506fc4611brefs/remotes/origin/master096f6a0030aa5a384df7466b4b0fc7506fc4611b096f6a0030aa5a384df7466b4b0fc7506fc4611brefs/remotes/origin/master096f6a0030aa5a384df7466b4b0fc7506fc4611b096f6a0030aa5a384df7466b4b0fc7506fc4611brefs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundfalse#159487255update-osmo-ci-on-slaves-dp #159159falsefalse159364156SUCCESS1610336166758https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/159/build2-deb9build-ansible- ttcn3-gbproxy-test/jenkins.shttcn3-gbproxy-test-fr/jenkins.sh096f6a0030aa5a384df7466b4b0fc7506fc4611b1610121097000https://jenkins.osmocom.org/jenkins/user/dwillmanndwillmanndwillmann@sysmocom.dettcn3-gbproxy-test: Fix pcap capture with dumpcap
In commit 2279aac6 dumpcap is used to capture pcaps, but dumpcap fails
if the directory isn't writable for everyone.
Commit 62ac27779 only fixed this issue for frame relay, this simply
mirrors the change for ttcn3-gbproxy-test
Change-Id: I11dcf9efd0b06544a82e31dec03fe76e182fd0d3
Related: OS#4518 SYS#5115
2021-01-08 16:51:37 +0100096f6a0030aa5a384df7466b4b0fc7506fc4611bttcn3-gbproxy-test: Fix pcap capture with dumpcapeditttcn3-gbproxy-test-fr/jenkins.sheditttcn3-gbproxy-test/jenkins.sh
githttps://jenkins.osmocom.org/jenkins/user/dwillmanndwillmann