Skip to content
Success

Console Output

Started by upstream project "gerrit-osmo-s1gw" build number 480
originally caused by:
 Triggered by Gerrit: https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/41099 in silent mode.
Running as SYSTEM
Building on the built-in node in workspace /var/jenkins_home/jobs/gerrit-osmo-s1gw-build/workspace@14
The recommended git tool is: NONE
using credential d5eda5e9-b59d-44ba-88d2-43473cb6e42d
Cloning the remote Git repository
Cloning repository ssh://jenkins@gerrit.osmocom.org:29418/erlang/osmo-s1gw
 > git init /var/jenkins_home/jobs/gerrit-osmo-s1gw-build/workspace@14 # timeout=10
Fetching upstream changes from ssh://jenkins@gerrit.osmocom.org:29418/erlang/osmo-s1gw
 > git --version # timeout=10
 > git --version # 'git version 2.39.5'
using GIT_SSH to set credentials gerrit.osmocom.org
Verifying host key using known hosts file, will automatically accept unseen keys
 > git fetch --tags --force --progress -- ssh://jenkins@gerrit.osmocom.org:29418/erlang/osmo-s1gw +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url ssh://jenkins@gerrit.osmocom.org:29418/erlang/osmo-s1gw # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url ssh://jenkins@gerrit.osmocom.org:29418/erlang/osmo-s1gw # timeout=10
Fetching upstream changes from ssh://jenkins@gerrit.osmocom.org:29418/erlang/osmo-s1gw
using GIT_SSH to set credentials gerrit.osmocom.org
Verifying host key using known hosts file, will automatically accept unseen keys
 > git fetch --tags --force --progress -- ssh://jenkins@gerrit.osmocom.org:29418/erlang/osmo-s1gw refs/changes/99/41099/3 # timeout=10
 > git rev-parse FETCH_HEAD^{commit} # timeout=10
Checking out Revision f03e3a7dfafdbafd1da8401091990af0d385bc4b (master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f f03e3a7dfafdbafd1da8401091990af0d385bc4b # timeout=10
Commit message: "[REST] Implement MetricsList"
 > git rev-parse FETCH_HEAD^{commit} # timeout=10
 > git rev-list --no-walk 3831f93404b7d98a5e3378e5e5397be7b68d3fd8 # timeout=10
Triggering gerrit-osmo-s1gw-build » a1=default,a2=default,a3=default,a4=default,osmocom-gerrit
Configuration gerrit-osmo-s1gw-build » a1=default,a2=default,a3=default,a4=default,osmocom-gerrit is still in the queue: Waiting for next available executor on ‘osmocom-gerrit’
Configuration gerrit-osmo-s1gw-build » a1=default,a2=default,a3=default,a4=default,osmocom-gerrit is still in the queue: Executor slot already in use
‘gtp0-deb10fr’ doesn’t have label ‘osmocom-gerrit’
‘lx2-raspbian12build-ansible’ doesn’t have label ‘osmocom-gerrit’
‘octsimtest’ doesn’t have label ‘osmocom-gerrit’
‘osmo-gsm-tester-prod’ doesn’t have label ‘osmocom-gerrit’
‘osmo-gsm-tester-rnd’ doesn’t have label ‘osmocom-gerrit’
‘rpi4-raspbian12build-ansible-1’ doesn’t have label ‘osmocom-gerrit’
‘rpi4-raspbian12build-ansible-2’ doesn’t have label ‘osmocom-gerrit’
‘rpi4-raspbian12build-ansible-3’ doesn’t have label ‘osmocom-gerrit’
‘simtester’ doesn’t have label ‘osmocom-gerrit’
Configuration gerrit-osmo-s1gw-build » a1=default,a2=default,a3=default,a4=default,osmocom-gerrit is still in the queue: Waiting for next available executor on ‘osmocom-gerritgerrit-osmo-s1gw-build » a1=default,a2=default,a3=default,a4=default,osmocom-gerrit completed with result SUCCESS
Finished: SUCCESS