Started by upstream project "<a href='/jenkins/job/master-libosmocore/' class='jenkins-table__link model-link model-link--float'>master-libosmocore</a>" build number <a href='/jenkins/job/master-libosmocore/4465' class='jenkins-table__link model-link model-link--float'>4465</a>
originally caused by:
 Started by timer
Running as SYSTEM
Building on the built-in node in workspace /var/jenkins_home/jobs/master-libosmo-netif/workspace
[ssh-agent] Looking for ssh-agent implementation...
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-Oao0mqPBOQf7/agent.847795
SSH_AGENT_PID=847803
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /var/jenkins_home/jobs/master-libosmo-netif/workspace@tmp/private_key_13996174204335793048.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-libosmo-netif/workspace/.git # timeout=10
Fetching changes from the remote Git repository
 &gt; git config remote.origin.url <a href='https://gerrit.osmocom.org/libosmo-netif'>https://gerrit.osmocom.org/libosmo-netif</a> # timeout=10
Fetching upstream changes from <a href='https://gerrit.osmocom.org/libosmo-netif'>https://gerrit.osmocom.org/libosmo-netif</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/libosmo-netif'>https://gerrit.osmocom.org/libosmo-netif</a> +refs/heads/*:refs/remotes/origin/* # timeout=10
 &gt; git rev-parse origin/master^{commit} # timeout=10
Checking out Revision c49977d48bc9f18d4124caae3e65f860ebc28136 (origin/master)
 &gt; git config core.sparsecheckout # timeout=10
 &gt; git checkout -f c49977d48bc9f18d4124caae3e65f860ebc28136 # timeout=10
Commit message: "Use %zu for size_t"
 &gt; git rev-list --no-walk c49977d48bc9f18d4124caae3e65f860ebc28136 # timeout=10
Triggering <a href='/jenkins/job/master-libosmo-netif/a1=default,a2=default,a3=default,a4=default,label=osmocom-master/' class='jenkins-table__link model-link model-link--float'>master-libosmo-netif » a1=default,a2=default,a3=default,a4=default,osmocom-master</a>
Configuration <a href='/jenkins/job/master-libosmo-netif/a1=default,a2=default,a3=default,a4=default,label=osmocom-master/' class='jenkins-table__link model-link model-link--float'>master-libosmo-netif » a1=default,a2=default,a3=default,a4=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-libosmo-netif/a1=default,a2=default,a3=default,a4=default,label=osmocom-master/' class='jenkins-table__link model-link model-link--float'>master-libosmo-netif » a1=default,a2=default,a3=default,a4=default,osmocom-master</a> completed with result SUCCESS
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 847803 killed;
[ssh-agent] Stopped.
Triggering a new build of <a href='/jenkins/job/Osmocom_OBS_master/' class='jenkins-table__link model-link model-link--float'>Osmocom_OBS_master</a>
Finished: SUCCESS