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 be74f32db1ff2a86805abf9866cf65da50d5232c (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f be74f32db1ff2a86805abf9866cf65da50d5232c # timeout=10
Commit message: "gerrit_binpkgs: display hint for OBS build status"
> git rev-list --no-walk be74f32db1ff2a86805abf9866cf65da50d5232c # 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 FAILURE
Configuration update-osmo-ci-on-slaves » gtp0-deb10fr is still in the queue: ‘gtp0-deb10fr’ is offline
Configuration update-osmo-ci-on-slaves » gtp0-deb10fr is still in the queue: ‘build2-deb10build-ansible’ doesn’t have label ‘gtp0-deb10fr’
‘build2-deb11build-ansible’ doesn’t have label ‘gtp0-deb10fr’
‘build4-deb12build-ansible’ doesn’t have label ‘gtp0-deb10fr’
‘gtp0-deb10fr’ is offline
‘host2-deb11build-ansible’ doesn’t have label ‘gtp0-deb10fr’
‘lx2-raspbian11build-ansible’ doesn’t have label ‘gtp0-deb10fr’
‘octsimtest’ doesn’t have label ‘gtp0-deb10fr’
‘osmo-gsm-tester-prod’ doesn’t have label ‘gtp0-deb10fr’
‘osmo-gsm-tester-rnd’ doesn’t have label ‘gtp0-deb10fr’
‘rpi4-raspbian12build-ansible-1’ doesn’t have label ‘gtp0-deb10fr’
‘rpi4-raspbian12build-ansible-2’ doesn’t have label ‘gtp0-deb10fr’
‘rpi4-raspbian12build-ansible-3’ doesn’t have label ‘gtp0-deb10fr’
‘simtester’ doesn’t have label ‘gtp0-deb10fr’
update-osmo-ci-on-slaves » gtp0-deb10fr completed with result SUCCESS
update-osmo-ci-on-slaves » host2-deb11build-ansible completed with result SUCCESS
update-osmo-ci-on-slaves » build2-deb10build-ansible completed with result SUCCESS
update-osmo-ci-on-slaves » build2-deb11build-ansible completed with result SUCCESS
update-osmo-ci-on-slaves » rpi4-raspbian12build-ansible-3 completed with result FAILURE
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 FAILURE
Finished: FAILURE