Started by an SCM change Running as SYSTEM Building on the built-in node in workspace /var/jenkins_home/jobs/master-libosmo-pfcp/workspace [ssh-agent] Looking for ssh-agent implementation... $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-XXXXXXyJxVpr/agent.1440193 SSH_AGENT_PID=1440196 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /var/jenkins_home/jobs/master-libosmo-pfcp/workspace@tmp/private_key_14600630315332396920.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-pfcp/workspace/.git # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://gerrit.osmocom.org/libosmo-pfcp # timeout=10 Fetching upstream changes from https://gerrit.osmocom.org/libosmo-pfcp > git --version # timeout=10 > git --version # 'git version 2.39.5' > git fetch --tags --force --progress -- https://gerrit.osmocom.org/libosmo-pfcp +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision d84872e6f919c6cdd67b006a5c4e2492f0edf907 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f d84872e6f919c6cdd67b006a5c4e2492f0edf907 # timeout=10 Commit message: "pfcp: add API osmo_pfcp_cp_peer_set_associated_cb()" > git rev-list --no-walk c4dcc1575612eb9670ae8bc51b4bd4c425062927 # timeout=10 Triggering master-libosmo-pfcp » a1=default,a2=default,a3=default,a4=default,osmocom-master master-libosmo-pfcp » 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 1440196 killed; [ssh-agent] Stopped. Triggering a new build of Osmocom_OBS_master Triggering a new build of master-osmo-hnbgw Triggering a new build of master-osmo-upf Finished: SUCCESS