Console Output

Started by timer
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.5'
 > 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 becb9cb6e8efdfcdc91ce7a5ccdae938ec457b3c (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f becb9cb6e8efdfcdc91ce7a5ccdae938ec457b3c # timeout=10
Commit message: "jobs/master-builds: archive android-apdu-proxy apk"
 > git rev-list --no-walk becb9cb6e8efdfcdc91ce7a5ccdae938ec457b3c # timeout=10
Triggering update-osmo-ci-on-slaves » rpi4-raspbian12build-ansible-1
Triggering update-osmo-ci-on-slaves » gtp0-deb10fr
Triggering update-osmo-ci-on-slaves » host2-deb11build-ansible
Triggering update-osmo-ci-on-slaves » build2-deb10build-ansible
Triggering update-osmo-ci-on-slaves » build2-deb11build-ansible
Triggering update-osmo-ci-on-slaves » rpi4-raspbian12build-ansible-3
Triggering update-osmo-ci-on-slaves » lx2-raspbian11build-ansible
Triggering update-osmo-ci-on-slaves » build4-deb12build-ansible
Triggering update-osmo-ci-on-slaves » simtester
Triggering update-osmo-ci-on-slaves » rpi4-raspbian12build-ansible-2
update-osmo-ci-on-slaves » rpi4-raspbian12build-ansible-1 completed with result SUCCESS
update-osmo-ci-on-slaves » gtp0-deb10fr completed with result SUCCESS
Configuration update-osmo-ci-on-slaves » host2-deb11build-ansible is still in the queue: Waiting for next available executor on ‘host2-deb11build-ansible’
update-osmo-ci-on-slaves » host2-deb11build-ansible completed with result SUCCESS
Configuration update-osmo-ci-on-slaves » build2-deb10build-ansible is still in the queue: Waiting for next available executor on ‘build2-deb10build-ansible’
update-osmo-ci-on-slaves » build2-deb10build-ansible completed with result SUCCESS
update-osmo-ci-on-slaves » build2-deb11build-ansible completed with result SUCCESS
Configuration update-osmo-ci-on-slaves » rpi4-raspbian12build-ansible-3 is still in the queue: Waiting for next available executor on ‘rpi4-raspbian12build-ansible-3’
update-osmo-ci-on-slaves » rpi4-raspbian12build-ansible-3 completed with result SUCCESS
update-osmo-ci-on-slaves » lx2-raspbian11build-ansible completed with result SUCCESS
update-osmo-ci-on-slaves » build4-deb12build-ansible completed with result SUCCESS
update-osmo-ci-on-slaves » simtester completed with result SUCCESS
update-osmo-ci-on-slaves » rpi4-raspbian12build-ansible-2 completed with result SUCCESS
Finished: SUCCESS