Started by an SCM change Running as SYSTEM Building on the built-in node in workspace /var/jenkins_home/jobs/master-libosmo-abis/workspace [ssh-agent] Looking for ssh-agent implementation... $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-XXXXXX5QAMVx/agent.89022 SSH_AGENT_PID=89025 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /var/jenkins_home/jobs/master-libosmo-abis/workspace@tmp/private_key_13128883488834389973.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-libosmo-abis/workspace/.git # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://gerrit.osmocom.org/libosmo-abis # timeout=10 Fetching upstream changes from https://gerrit.osmocom.org/libosmo-abis > git --version # timeout=10 > git --version # 'git version 2.39.5' > git fetch --tags --force --progress -- https://gerrit.osmocom.org/libosmo-abis +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision f8498f823d85f696906a5da0268d2e159d12a315 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f f8498f823d85f696906a5da0268d2e159d12a315 # timeout=10 Commit message: "e1_input: Guard against crash by users calling reentrant e1inp_sign_link_destroy()" > git rev-list --no-walk 6cf4ebb9f20fb5183f076a0ae23865940efa89c8 # timeout=10 Triggering master-libosmo-abis » a1=default,a2=default,a3=default,a4=default,osmocom-master master-libosmo-abis » 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 89025 killed; [ssh-agent] Stopped. Triggering a new build of Osmocom_OBS_master Triggering a new build of master-osmo-sgsn Triggering a new build of master-osmo-hlr Triggering a new build of master-osmo-bts Triggering a new build of master-osmo-mgw Finished: SUCCESS