Started by upstream project "master-libosmocore" build number 4718 originally caused by: Started by an SCM change Running as SYSTEM Building on the built-in node in workspace /var/jenkins_home/jobs/master-osmocom-bb/workspace [ssh-agent] Looking for ssh-agent implementation... $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-rjZ4RjSIQgLJ/agent.4173829 SSH_AGENT_PID=4173832 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /var/jenkins_home/jobs/master-osmocom-bb/workspace@tmp/private_key_10772695971345655783.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-osmocom-bb/workspace/.git # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://gerrit.osmocom.org/osmocom-bb # timeout=10 Fetching upstream changes from https://gerrit.osmocom.org/osmocom-bb > git --version # timeout=10 > git --version # 'git version 2.47.3' > git fetch --tags --force --progress -- https://gerrit.osmocom.org/osmocom-bb +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision daa94dbc0821231e7f8453f0ace97f91fa0c75f6 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f daa94dbc0821231e7f8453f0ace97f91fa0c75f6 # timeout=10 Commit message: "mobile: gsm48_mmxx_msg_names[]: fix some strings" > git rev-list --no-walk daa94dbc0821231e7f8453f0ace97f91fa0c75f6 # timeout=10 Triggering master-osmocom-bb » a1=default,a2=default,a3=default,a4=default,osmocom-master Configuration master-osmocom-bb » 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-osmocom-bb » 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’ ‘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’ Configuration master-osmocom-bb » 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-osmocom-bb » 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’ ‘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’ Configuration master-osmocom-bb » a1=default,a2=default,a3=default,a4=default,osmocom-master is still in the queue: Waiting for next available executor on ‘osmocom-master’ master-osmocom-bb » 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 4173832 killed; [ssh-agent] Stopped. Triggering a new build of Osmocom_OBS_master Triggering a new build of osmo-gsm-tester_build-osmocom-bb Finished: SUCCESS