Started by upstream project "master-libosmocore" build number 4280
originally caused by:
 Started by an SCM change
Running as SYSTEM
Building on the built-in node in workspace /var/jenkins_home/jobs/master-osmo-gbproxy/workspace
[ssh-agent] Looking for ssh-agent implementation...
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXWGiQEb/agent.2751472
SSH_AGENT_PID=2751477
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /var/jenkins_home/jobs/master-osmo-gbproxy/workspace@tmp/private_key_6960308624482974216.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-gbproxy/workspace/.git # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://gerrit.osmocom.org/osmo-gbproxy # timeout=10
Fetching upstream changes from https://gerrit.osmocom.org/osmo-gbproxy
 > git --version # timeout=10
 > git --version # 'git version 2.39.5'
 > git fetch --tags --force --progress -- https://gerrit.osmocom.org/osmo-gbproxy +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 0aee821e141916c386c013b70c60a3609ec2b9e7 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0aee821e141916c386c013b70c60a3609ec2b9e7 # timeout=10
Commit message: "jenkins.sh: Use --disable-doxygen configure param"
 > git rev-list --no-walk 0aee821e141916c386c013b70c60a3609ec2b9e7 # timeout=10
Triggering master-osmo-gbproxy » a1=default,a2=default,a3=default,a4=default,osmocom-master
Configuration master-osmo-gbproxy » 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-gbproxy » a1=default,a2=default,a3=default,a4=default,osmocom-master is still in the queue: Executor slot already in use
‘gtp0-deb10fr’ doesn’t have label ‘osmocom-master’
‘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-2’ doesn’t have label ‘osmocom-master’
‘simtester’ doesn’t have label ‘osmocom-master’
Configuration master-osmo-gbproxy » a1=default,a2=default,a3=default,a4=default,osmocom-master is still in the queue: Waiting for next available executor on ‘osmocom-master’
master-osmo-gbproxy » 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 2751477 killed;
[ssh-agent] Stopped.
Triggering a new build of Osmocom_OBS_master
Finished: SUCCESS