Started by an SCM change
Running as SYSTEM
Building on the built-in node in workspace /var/jenkins_home/jobs/master-ot290-gsmtap/workspace
[ssh-agent] Looking for ssh-agent implementation...
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXE42F41/agent.1167565
SSH_AGENT_PID=1167568
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /var/jenkins_home/jobs/master-ot290-gsmtap/workspace@tmp/private_key_12729410788532531011.key (osmocom-jenkins)
[ssh-agent] Using credentials docs (OS#5798)
The recommended git tool is: NONE
No credentials specified
Cloning the remote Git repository
Cloning repository <a href='https://gitea.osmocom.org/phone-side/ot290-gsmtap'>https://gitea.osmocom.org/phone-side/ot290-gsmtap</a>
 &gt; git init /var/jenkins_home/jobs/master-ot290-gsmtap/workspace # timeout=10
Fetching upstream changes from <a href='https://gitea.osmocom.org/phone-side/ot290-gsmtap'>https://gitea.osmocom.org/phone-side/ot290-gsmtap</a>
 &gt; git --version # timeout=10
 &gt; git --version # 'git version 2.39.5'
 &gt; git fetch --tags --force --progress -- <a href='https://gitea.osmocom.org/phone-side/ot290-gsmtap'>https://gitea.osmocom.org/phone-side/ot290-gsmtap</a> +refs/heads/*:refs/remotes/origin/* # timeout=10
 &gt; git config remote.origin.url <a href='https://gitea.osmocom.org/phone-side/ot290-gsmtap'>https://gitea.osmocom.org/phone-side/ot290-gsmtap</a> # timeout=10
 &gt; git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
 &gt; git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 377cd66473c3e43e79866281dff918748b4a33f1 (origin/master)
 &gt; git config core.sparsecheckout # timeout=10
 &gt; git checkout -f 377cd66473c3e43e79866281dff918748b4a33f1 # timeout=10
Commit message: "now it is specified whether the packet is uplink or downlink"
First time build. Skipping changelog.
Triggering <a href='/jenkins/job/master-ot290-gsmtap/a1=default,a2=default,a3=default,a4=default,label=osmocom-master/' class='jenkins-table__link model-link model-link--float'>master-ot290-gsmtap » a1=default,a2=default,a3=default,a4=default,osmocom-master</a>
Configuration <a href='/jenkins/job/master-ot290-gsmtap/a1=default,a2=default,a3=default,a4=default,label=osmocom-master/' class='jenkins-table__link model-link model-link--float'>master-ot290-gsmtap » 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-ot290-gsmtap/a1=default,a2=default,a3=default,a4=default,label=osmocom-master/' class='jenkins-table__link model-link model-link--float'>master-ot290-gsmtap » 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 1167568 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