Started by an SCM change Running as SYSTEM Building on the built-in node in workspace /var/jenkins_home/jobs/update-osmo-ci-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/osmo-ci > git init /var/jenkins_home/jobs/update-osmo-ci-on-slaves/workspace # timeout=10 Fetching upstream changes from https://gerrit.osmocom.org/osmo-ci > git --version # timeout=10 > git --version # 'git version 2.39.2' > git fetch --tags --force --progress -- https://gerrit.osmocom.org/osmo-ci +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://gerrit.osmocom.org/osmo-ci # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 Avoid second fetch > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision cf3cbf38857cbabf6d242599a347fae90f90a7ae (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f cf3cbf38857cbabf6d242599a347fae90f90a7ae # timeout=10 Commit message: "OBS: gerrit_binpkgs: add hint where to find pkgs" > git rev-list --no-walk 91a79bd8aa8e7901a7d687b6222df360db1bcdc5 # timeout=10 Triggering update-osmo-ci-on-slaves » host2-deb11build-ansible Triggering update-osmo-ci-on-slaves » simtester Triggering update-osmo-ci-on-slaves » build2-deb11build-ansible Triggering update-osmo-ci-on-slaves » build2-deb10build-ansible Triggering update-osmo-ci-on-slaves » rpi4-raspbian11build-ansible-1 Triggering update-osmo-ci-on-slaves » build4-deb12build-ansible Triggering update-osmo-ci-on-slaves » rpi4-raspbian11build-ansible-2 Triggering update-osmo-ci-on-slaves » rpi4-raspbian11build-ansible-3 Triggering update-osmo-ci-on-slaves » gtp0-deb10fr update-osmo-ci-on-slaves » host2-deb11build-ansible completed with result SUCCESS update-osmo-ci-on-slaves » simtester completed with result SUCCESS update-osmo-ci-on-slaves » build2-deb11build-ansible completed with result SUCCESS update-osmo-ci-on-slaves » build2-deb10build-ansible completed with result SUCCESS Configuration update-osmo-ci-on-slaves » rpi4-raspbian11build-ansible-1 is still in the queue: Waiting for next available executor on ‘rpi4-raspbian11build-ansible-1’ update-osmo-ci-on-slaves » rpi4-raspbian11build-ansible-1 completed with result SUCCESS update-osmo-ci-on-slaves » build4-deb12build-ansible completed with result SUCCESS update-osmo-ci-on-slaves » rpi4-raspbian11build-ansible-2 completed with result SUCCESS update-osmo-ci-on-slaves » rpi4-raspbian11build-ansible-3 completed with result SUCCESS update-osmo-ci-on-slaves » gtp0-deb10fr completed with result SUCCESS Finished: SUCCESS