Started by an SCM change00443563561.0093789378664f17cc180134f69040a5b81645afc8c98c7c12ff7f17cc180134f69040a5b81645afc8c98c7c12ff7origin/masterf17cc180134f69040a5b81645afc8c98c7c12ff7f17cc180134f69040a5b81645afc8c98c7c12ff7origin/master65795ce281cbe3d76c80b9dbd2b206a9edf46f4296695ce281cbe3d76c80b9dbd2b206a9edf46f42966refs/remotes/origin/master95ce281cbe3d76c80b9dbd2b206a9edf46f4296695ce281cbe3d76c80b9dbd2b206a9edf46f42966refs/remotes/origin/masterf17cc180134f69040a5b81645afc8c98c7c12ff7f17cc180134f69040a5b81645afc8c98c7c12ff7origin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#664356255update-osmo-ci-on-slaves-dp #664664falsefalse6641954812SUCCESS1753964469809https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/664/build5-deb12build-ansible- common/respawn.shttcn3-bts-test/jenkins.shf17cc180134f69040a5b81645afc8c98c7c12ff71753951646000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dettcn3-bts-test: show respawn count at the end
As mentioned in the last commit, we currently must use respawn.sh to be
able to recover from clock skew errors seen in jenkins. Let's display
the respawn count at the end as warning.
Related: OS#6794
Change-Id: I4e5c3dd46ec682bfd79f2328195b0050fe3f186d
2025-07-31 10:47:26 +0200f17cc180134f69040a5b81645afc8c98c7c12ff7ttcn3-bts-test: show respawn count at the endeditttcn3-bts-test/jenkins.sheditcommon/respawn.sh
githttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith