Started by an SCM change00443833831.091979197095809189918963857f680439f378f5bb5c6582297ae0636db6650f857f680439f378f5bb5c6582297ae0636db6650f8refs/remotes/origin/master57f680439f378f5bb5c6582297ae0636db6650f857f680439f378f5bb5c6582297ae0636db6650f8refs/remotes/origin/master57f680439f378f5bb5c6582297ae0636db6650f857f680439f378f5bb5c6582297ae0636db6650f8refs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundhttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/638/artifacthttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/changeshttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/638/https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/638/testReportfalse#638383255update-osmo-ci-on-slaves-dp #638638falsefalse6381826298SUCCESS1740485769617https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/638/build5-deb12build-ansiblettcn3-bts-test/jenkins.sh57f680439f378f5bb5c6582297ae0636db6650f81740485565000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgttcn3-bts-test: do not use respawn.sh Re-spawning osmo-bts is no longer necessary. For quite some time now, it has been able to attempt OML link re-establishment in a loop instead of exit()ing. Additionally, using respawn.sh makes crashes harder to detect. Whether we should restart the IUT process and continue executing the remaining test cases after a crash is debatable. However, none of the other testsuites (except ttcn3-pcu-test, which actually requires restarting osmo-pcu after each TC) use respawn.sh for that purpose. Change-Id: I770a0530f90c5e03d2073bfc1c4cfd0e840379c9 Related: OS#6728, OS#6729 2025-02-25 12:12:45 +000057f680439f378f5bb5c6582297ae0636db6650f8ttcn3-bts-test: do not use respawn.sheditttcn3-bts-test/jenkins.shgithttps://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge