Started by an SCM change00113243241.0069696969541d7c50db104de763ba44a0b81c99321b39aa33e0ed7c50db104de763ba44a0b81c99321b39aa33e0erefs/remotes/origin/masterd7c50db104de763ba44a0b81c99321b39aa33e0ed7c50db104de763ba44a0b81c99321b39aa33e0erefs/remotes/origin/masterd7c50db104de763ba44a0b81c99321b39aa33e0ed7c50db104de763ba44a0b81c99321b39aa33e0erefs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#541324255update-osmo-ci-on-slaves-dp #541541falsefalse5411500284SUCCESS1711375267909https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/541/build2-deb11build-ansible- ttcn3-ggsn-test/jenkins.shd7c50db104de763ba44a0b81c99321b39aa33e0e1711375007000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dettcn3-ggsn-test: ignore failure to kill osmo-ggsn
Don't fail if osmo-ggsn can't be killed at the end of a testsuite
run. This happens currently with ttcn3-ggsn-test-kernel-latest-* jobs,
in the v6_only configurations, because osmo-ggsn latest doesn't support
ipv6 yet and exits. The jenkins.sh should keep going and try other
combinations, and exit without error in the end.
Fixes: d8c51cce ("ttcn3-ggsn-test: run with multiple configurations")
Change-Id: I6f3154a9ef114f31bcb5868ee09d1ebc10f35d07
2024-03-25 13:56:47 +0000d7c50db104de763ba44a0b81c99321b39aa33e0ettcn3-ggsn-test: ignore failure to kill osmo-ggsneditttcn3-ggsn-test/jenkins.sh
githttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith