Skip to content
Success

Console Output

Started by timer
Running as SYSTEM
Building on the built-in node in workspace /var/jenkins_home/jobs/master-osmo-hnodeb/workspace@2
[ssh-agent] Looking for ssh-agent implementation...
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXohf4pJ/agent.1161320
SSH_AGENT_PID=1161323
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /var/jenkins_home/jobs/master-osmo-hnodeb/workspace@2@tmp/private_key_198268805646188225.key (osmocom-jenkins)
[ssh-agent] Using credentials docs (OS#5798)
The recommended git tool is: NONE
No credentials specified
 > git rev-parse --resolve-git-dir /var/jenkins_home/jobs/master-osmo-hnodeb/workspace@2/.git # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://gerrit.osmocom.org/osmo-hnodeb # timeout=10
Fetching upstream changes from https://gerrit.osmocom.org/osmo-hnodeb
 > git --version # timeout=10
 > git --version # 'git version 2.39.5'
 > git fetch --tags --force --progress -- https://gerrit.osmocom.org/osmo-hnodeb +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision ffed493dafacb376f1964414b4659ea19684b775 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f ffed493dafacb376f1964414b4659ea19684b775 # timeout=10
Commit message: "jenkins.sh: No need to build libosmo-sigtran with doxygen"
 > git rev-list --no-walk ffed493dafacb376f1964414b4659ea19684b775 # timeout=10
Triggering master-osmo-hnodeb » a1=default,a2=default,a3=default,a4=default,osmocom-master
Configuration master-osmo-hnodeb » a1=default,a2=default,a3=default,a4=default,osmocom-master is still in the queue: Waiting for next available executor on ‘osmocom-master’
Configuration master-osmo-hnodeb » a1=default,a2=default,a3=default,a4=default,osmocom-master is still in the queue: ‘build2-deb10build-ansible’ is offline
‘build2-deb11build-ansible’ is offline
‘build5-deb12build-ansible’ is offline
‘gtp0-deb10fr’ doesn’t have label ‘osmocom-master’
‘host2-deb11build-ansible’ is offline
‘lx2-raspbian11build-ansible’ doesn’t have label ‘osmocom-master’
‘octsimtest’ doesn’t have label ‘osmocom-master’
‘osmo-gsm-tester-prod’ doesn’t have label ‘osmocom-master’
‘osmo-gsm-tester-rnd’ doesn’t have label ‘osmocom-master’
‘rpi4-raspbian12build-ansible-1’ doesn’t have label ‘osmocom-master’
‘rpi4-raspbian12build-ansible-2’ doesn’t have label ‘osmocom-master’
‘rpi4-raspbian12build-ansible-3’ doesn’t have label ‘osmocom-master’
‘simtester’ doesn’t have label ‘osmocom-master’
Configuration master-osmo-hnodeb » a1=default,a2=default,a3=default,a4=default,osmocom-master is still in the queue: Waiting for next available executor on ‘osmocom-master’
Configuration master-osmo-hnodeb » a1=default,a2=default,a3=default,a4=default,osmocom-master is still in the queue: Executor slot already in use
‘build2-deb10build-ansible’ is offline
‘build2-deb11build-ansible’ is offline
‘gtp0-deb10fr’ doesn’t have label ‘osmocom-master’
‘host2-deb11build-ansible’ is offline
‘lx2-raspbian11build-ansible’ doesn’t have label ‘osmocom-master’
‘octsimtest’ doesn’t have label ‘osmocom-master’
‘osmo-gsm-tester-prod’ doesn’t have label ‘osmocom-master’
‘osmo-gsm-tester-rnd’ doesn’t have label ‘osmocom-master’
‘rpi4-raspbian12build-ansible-1’ doesn’t have label ‘osmocom-master’
‘rpi4-raspbian12build-ansible-2’ doesn’t have label ‘osmocom-master’
‘rpi4-raspbian12build-ansible-3’ doesn’t have label ‘osmocom-master’
‘simtester’ doesn’t have label ‘osmocom-master’
master-osmo-hnodeb » a1=default,a2=default,a3=default,a4=default,osmocom-master completed with result SUCCESS
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 1161323 killed;
[ssh-agent] Stopped.
Triggering a new build of Osmocom_OBS_master
Finished: SUCCESS