Skip to content

Console Output

Started by upstream project "update-osmo-ci-on-slaves-dp" build number 548
originally caused by:
 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 a307c7df718af05d978a65cd96a51138fb1b4d31 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f a307c7df718af05d978a65cd96a51138fb1b4d31 # timeout=10
Commit message: "jobs/gerrit,master: osmo-hnbgw: add nftables var"
 > git rev-list --no-walk afd9d56e0568a61d0b2de010f710baffb71bff25 # 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
Configuration update-osmo-ci-on-slaves » simtester is still in the queue: Waiting for next available executor on ‘simtesterupdate-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
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