Started by an SCM change00443343341.00685368536635342050873eaca13841928a34fd358ca2fe51e1c5342050873eaca13841928a34fd358ca2fe51e1corigin/master5342050873eaca13841928a34fd358ca2fe51e1c5342050873eaca13841928a34fd358ca2fe51e1corigin/master65795ce281cbe3d76c80b9dbd2b206a9edf46f4296695ce281cbe3d76c80b9dbd2b206a9edf46f42966refs/remotes/origin/master95ce281cbe3d76c80b9dbd2b206a9edf46f4296695ce281cbe3d76c80b9dbd2b206a9edf46f42966refs/remotes/origin/master5342050873eaca13841928a34fd358ca2fe51e1c5342050873eaca13841928a34fd358ca2fe51e1corigin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#663334255update-osmo-ci-on-slaves-dp #663663falsefalse6631954066SUCCESS1753888567203https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/663/build5-deb12build-ansible- ttcn3-bts-test/jenkins.sh5342050873eaca13841928a34fd358ca2fe51e1c1753875090000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deRevert "ttcn3-bts-test: do not use respawn.sh"
This reverts commit 57f680439f378f5bb5c6582297ae0636db6650f8.
We're observing a lot of turbulence in ttcn3-bts-test due to the
clock instability:
Shutting down BTS, exit 1, reason: PC clock skew too high
Even though it's no longer necessary to respawn osmo-bts-trx,
let's restore the respawn.sh to recover from such failures.
Related: OS#6794
Change-Id: I1177e9068c49bf31a4010cd21700839dfa8d5050
2025-07-30 13:31:30 +02005342050873eaca13841928a34fd358ca2fe51e1cRevert "ttcn3-bts-test: do not use respawn.sh"editttcn3-bts-test/jenkins.sh
githttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith