![[Jenkins]](/jenkins/static/342c126a/images/svgs/logo.svg){kind=logo}
Started by an SCM change Running as SYSTEM Building on the built-in node in workspace /var/jenkins_home/jobs/update-osmo-python-on-slaves/workspace The recommended git tool is: NONE No credentials specified Wiping out workspace first. Cloning the remote Git repository Cloning repository https://gerrit.osmocom.org/python/osmo-python-tests > git init /var/jenkins_home/jobs/update-osmo-python-on-slaves/workspace # timeout=10 Fetching upstream changes from https://gerrit.osmocom.org/python/osmo-python-tests > git --version # timeout=10 > git --version # 'git version 2.39.2' > git fetch --tags --force --progress -- https://gerrit.osmocom.org/python/osmo-python-tests +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://gerrit.osmocom.org/python/osmo-python-tests # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 Avoid second fetch > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 Checking out Revision bee2f36c96bcca48df0c2c397f29e7d8a879dcf0 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f bee2f36c96bcca48df0c2c397f29e7d8a879dcf0 # timeout=10 Commit message: "scripts/osmotestconfig: remove_tmpdir -> shutil.rmtree" > git rev-list --no-walk b15d2af6ed534c550a546493b5ff4c43d898e5f2 # timeout=10 Triggering update-osmo-python-on-slaves » rpi4-raspbian11build-ansible-2 Triggering update-osmo-python-on-slaves » build4-deb12build-ansible Triggering update-osmo-python-on-slaves » build2-deb11build-ansible Triggering update-osmo-python-on-slaves » host2-deb11build-ansible Triggering update-osmo-python-on-slaves » rpi4-raspbian11build-ansible-1 Triggering update-osmo-python-on-slaves » rpi4-raspbian11build-ansible-3 Triggering update-osmo-python-on-slaves » build2-deb10build-ansible update-osmo-python-on-slaves » rpi4-raspbian11build-ansible-2 completed with result SUCCESS update-osmo-python-on-slaves » build4-deb12build-ansible completed with result SUCCESS update-osmo-python-on-slaves » build2-deb11build-ansible completed with result SUCCESS update-osmo-python-on-slaves » host2-deb11build-ansible completed with result SUCCESS Configuration update-osmo-python-on-slaves » rpi4-raspbian11build-ansible-1 is still in the queue: Waiting for next available executor on ‘rpi4-raspbian11build-ansible-1’ update-osmo-python-on-slaves » rpi4-raspbian11build-ansible-1 completed with result SUCCESS update-osmo-python-on-slaves » rpi4-raspbian11build-ansible-3 completed with result SUCCESS update-osmo-python-on-slaves » build2-deb10build-ansible completed with result SUCCESS Triggering a new build of update-osmo-ci-on-slaves Finished: SUCCESS