Started by upstream project "<a href='/jenkins/job/master-libosmo-pfcp/' class='jenkins-table__link model-link model-link--float'>master-libosmo-pfcp</a>" build number <a href='/jenkins/job/master-libosmo-pfcp/2204' class='jenkins-table__link model-link model-link--float'>2204</a>
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-hnbgw/workspace
[ssh-agent] Looking for ssh-agent implementation...
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXbd3i3w/agent.1647849
SSH_AGENT_PID=1647857
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /var/jenkins_home/jobs/master-osmo-hnbgw/workspace@tmp/private_key_15836496784144524969.key (osmocom-jenkins)
[ssh-agent] Using credentials docs (OS#5798)
The recommended git tool is: NONE
No credentials specified
 &gt; git rev-parse --resolve-git-dir /var/jenkins_home/jobs/master-osmo-hnbgw/workspace/.git # timeout=10
Fetching changes from the remote Git repository
 &gt; git config remote.origin.url <a href='https://gerrit.osmocom.org/osmo-hnbgw'>https://gerrit.osmocom.org/osmo-hnbgw</a> # timeout=10
Fetching upstream changes from <a href='https://gerrit.osmocom.org/osmo-hnbgw'>https://gerrit.osmocom.org/osmo-hnbgw</a>
 &gt; git --version # timeout=10
 &gt; git --version # 'git version 2.39.5'
 &gt; git fetch --tags --force --progress -- <a href='https://gerrit.osmocom.org/osmo-hnbgw'>https://gerrit.osmocom.org/osmo-hnbgw</a> +refs/heads/*:refs/remotes/origin/* # timeout=10
 &gt; git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 1d4811e38c4359bdbd65e2961761d1e3e351bea9 (origin/master)
 &gt; git config core.sparsecheckout # timeout=10
 &gt; git checkout -f 1d4811e38c4359bdbd65e2961761d1e3e351bea9 # timeout=10
Commit message: "Add PFCP stats item group"
 &gt; git rev-list --no-walk 1d4811e38c4359bdbd65e2961761d1e3e351bea9 # timeout=10
Triggering <a href='/jenkins/job/master-osmo-hnbgw/NFTABLES=0,PFCP=0,WITH_MANUALS=0,a4=default,label=osmocom-master/' class='jenkins-table__link model-link model-link--float'>master-osmo-hnbgw » NFTABLES=0,PFCP=0,WITH_MANUALS=0,default,osmocom-master</a>
Triggering <a href='/jenkins/job/master-osmo-hnbgw/NFTABLES=1,PFCP=1,WITH_MANUALS=1,a4=default,label=osmocom-master/' class='jenkins-table__link model-link model-link--float'>master-osmo-hnbgw » NFTABLES=1,PFCP=1,WITH_MANUALS=1,default,osmocom-master</a>
Configuration <a href='/jenkins/job/master-osmo-hnbgw/NFTABLES=0,PFCP=0,WITH_MANUALS=0,a4=default,label=osmocom-master/' class='jenkins-table__link model-link model-link--float'>master-osmo-hnbgw » NFTABLES=0,PFCP=0,WITH_MANUALS=0,default,osmocom-master</a> is still in the queue: Waiting for next available executor on ‘<a href='/jenkins/label/osmocom-master/' class='jenkins-table__link model-link model-link--float'>osmocom-master</a>’
<a href='/jenkins/job/master-osmo-hnbgw/NFTABLES=0,PFCP=0,WITH_MANUALS=0,a4=default,label=osmocom-master/' class='jenkins-table__link model-link model-link--float'>master-osmo-hnbgw » NFTABLES=0,PFCP=0,WITH_MANUALS=0,default,osmocom-master</a> completed with result SUCCESS
<a href='/jenkins/job/master-osmo-hnbgw/NFTABLES=1,PFCP=1,WITH_MANUALS=1,a4=default,label=osmocom-master/' class='jenkins-table__link model-link model-link--float'>master-osmo-hnbgw » NFTABLES=1,PFCP=1,WITH_MANUALS=1,default,osmocom-master</a> completed with result FAILURE
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 1647857 killed;
[ssh-agent] Stopped.
Finished: FAILURE