Started by an SCM change00002532531.0080088008687290ae4c2e7eaaad3301a24803df2c7d0d3b51bcc290ae4c2e7eaaad3301a24803df2c7d0d3b51bccorigin/master290ae4c2e7eaaad3301a24803df2c7d0d3b51bcc290ae4c2e7eaaad3301a24803df2c7d0d3b51bccorigin/master65795ce281cbe3d76c80b9dbd2b206a9edf46f4296695ce281cbe3d76c80b9dbd2b206a9edf46f42966refs/remotes/origin/master95ce281cbe3d76c80b9dbd2b206a9edf46f4296695ce281cbe3d76c80b9dbd2b206a9edf46f42966refs/remotes/origin/master290ae4c2e7eaaad3301a24803df2c7d0d3b51bcc290ae4c2e7eaaad3301a24803df2c7d0d3b51bccorigin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#687253255update-osmo-ci-on-slaves-dp #687687falsefalse68743091SUCCESS1772005269005https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/687/build5-deb12build-ansiblettcn3-bts-test/jenkins.sh290ae4c2e7eaaad3301a24803df2c7d0d3b51bcc1771935760000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.dettcn3-bts-test: write bts logs to tmpfs Pau suggested in the related issue that we try to write the bts logs into tmpfs, instead of directly to ext4. This seems to cause the slow downs, which then result in clock skew errors. Related: SYS#6794#note-29 Change-Id: Id9a93f7149ef7e9bfde1f4fe3a8299ba46645d50 2026-02-24 13:22:40 +0100290ae4c2e7eaaad3301a24803df2c7d0d3b51bccttcn3-bts-test: write bts logs to tmpfseditttcn3-bts-test/jenkins.shgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith