Started by an SCM change Running as SYSTEM Building on the built-in node in workspace /var/jenkins_home/jobs/master-libosmocore/workspace [ssh-agent] Looking for ssh-agent implementation... $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-9e18DKunidAP/agent.3833227 SSH_AGENT_PID=3833230 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /var/jenkins_home/jobs/master-libosmocore/workspace@tmp/private_key_413261574654641507.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-libosmocore/workspace/.git # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://gerrit.osmocom.org/libosmocore # timeout=10 Fetching upstream changes from https://gerrit.osmocom.org/libosmocore > git --version # timeout=10 > git --version # 'git version 2.47.3' > git fetch --tags --force --progress -- https://gerrit.osmocom.org/libosmocore +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision b2337963a490c30f5596a5c96d9cf4db8ca08e93 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f b2337963a490c30f5596a5c96d9cf4db8ca08e93 # timeout=10 Commit message: "vty: guard definition of _XOPEN_SOURCE" > git rev-list --no-walk e2bff1fe44e68a588ccf3cd0fb4553eba6f03440 # timeout=10 Triggering master-libosmocore » a2=default,a3=default,a4=default,arm-none-eabi,io_uring Triggering master-libosmocore » a2=default,a3=default,a4=default,amd64,io_uring Configuration master-libosmocore » a2=default,a3=default,a4=default,arm-none-eabi,io_uring is still in the queue: Waiting for next available executor on ‘io_uring’ Configuration master-libosmocore » a2=default,a3=default,a4=default,arm-none-eabi,io_uring is still in the queue: Executor slot already in use ‘gtp0-deb10fr’ doesn’t have label ‘io_uring’ ‘lx2-raspbian12build-ansible’ doesn’t have label ‘io_uring’ ‘octsimtest’ doesn’t have label ‘io_uring’ ‘osmo-gsm-tester-prod’ doesn’t have label ‘io_uring’ ‘osmo-gsm-tester-rnd’ doesn’t have label ‘io_uring’ ‘rpi4-raspbian12build-ansible-1’ doesn’t have label ‘io_uring’ ‘rpi4-raspbian12build-ansible-2’ doesn’t have label ‘io_uring’ ‘simtester’ doesn’t have label ‘io_uring’ Configuration master-libosmocore » a2=default,a3=default,a4=default,arm-none-eabi,io_uring is still in the queue: Waiting for next available executor on ‘io_uring’ master-libosmocore » a2=default,a3=default,a4=default,arm-none-eabi,io_uring completed with result SUCCESS Configuration master-libosmocore » a2=default,a3=default,a4=default,amd64,io_uring is still in the queue: Waiting for next available executor on ‘io_uring’ master-libosmocore » a2=default,a3=default,a4=default,amd64,io_uring completed with result SUCCESS $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 3833230 killed; [ssh-agent] Stopped. Triggering a new build of Osmocom_OBS_master Triggering a new build of master-simtrace Triggering a new build of master-osmo-trx Triggering a new build of master-osmo-ggsn Triggering a new build of master-osmo-gmr Triggering a new build of master-osmocom-bb Triggering a new build of master-osmo-pcap Triggering a new build of master-osmo-tetra Triggering a new build of master-osmo-sip-connector Triggering a new build of master-libosmo-netif Triggering a new build of master-libosmo-pfcp Triggering a new build of master-osmo-gbproxy Triggering a new build of master-xgoldmon Finished: SUCCESS