Started by upstream project "<a href='/jenkins/job/gerrit-libosmocore/' class='jenkins-table__link model-link model-link--float'>gerrit-libosmocore</a>" build number <a href='/jenkins/job/gerrit-libosmocore/2328' class='jenkins-table__link model-link model-link--float'>2328</a>
originally caused by:
 Triggered by Gerrit: <a href='https://gerrit.osmocom.org/c/libosmocore/+/41985'>https://gerrit.osmocom.org/c/libosmocore/+/41985</a> in silent mode.
Running as SYSTEM
Building on the built-in node in workspace /var/jenkins_home/jobs/gerrit-libosmocore-build/workspace
The recommended git tool is: NONE
using credential d5eda5e9-b59d-44ba-88d2-43473cb6e42d
 &gt; git rev-parse --resolve-git-dir /var/jenkins_home/jobs/gerrit-libosmocore-build/workspace/.git # timeout=10
Fetching changes from the remote Git repository
 &gt; git config remote.origin.url ssh://jenkins@gerrit.osmocom.org:29418/libosmocore # timeout=10
Fetching upstream changes from ssh://jenkins@gerrit.osmocom.org:29418/libosmocore
 &gt; git --version # timeout=10
 &gt; git --version # 'git version 2.47.3'
using GIT_SSH to set credentials gerrit.osmocom.org
Verifying host key using known hosts file, will automatically accept unseen keys
 &gt; git fetch --tags --force --progress -- ssh://jenkins@gerrit.osmocom.org:29418/libosmocore refs/changes/85/41985/1 # timeout=10
 &gt; git rev-parse FETCH_HEAD^{commit} # timeout=10
Checking out Revision 20e691a3867a57ef80307f73974bbffb2f91e34b (master)
 &gt; git config core.sparsecheckout # timeout=10
 &gt; git checkout -f 20e691a3867a57ef80307f73974bbffb2f91e34b # timeout=10
Commit message: "vty: Use osmo_fd_{write,read}_enable() API helper"
 &gt; git rev-parse FETCH_HEAD^{commit} # timeout=10
 &gt; git rev-list --no-walk e9cb0eaddf677fd7e279578185468930bd0ee08e # timeout=10
Triggering <a href='/jenkins/job/gerrit-libosmocore-build/a2=default,a3=default,a4=default,arch=arm-none-eabi,label=io_uring/' class='jenkins-table__link model-link model-link--float'>gerrit-libosmocore-build » a2=default,a3=default,a4=default,arm-none-eabi,io_uring</a>
Triggering <a href='/jenkins/job/gerrit-libosmocore-build/a2=default,a3=default,a4=default,arch=amd64,label=io_uring/' class='jenkins-table__link model-link model-link--float'>gerrit-libosmocore-build » a2=default,a3=default,a4=default,amd64,io_uring</a>
Configuration <a href='/jenkins/job/gerrit-libosmocore-build/a2=default,a3=default,a4=default,arch=arm-none-eabi,label=io_uring/' class='jenkins-table__link model-link model-link--float'>gerrit-libosmocore-build » a2=default,a3=default,a4=default,arm-none-eabi,io_uring</a> is still in the queue: Waiting for next available executor on ‘<a href='/jenkins/label/io_uring/' class='jenkins-table__link model-link model-link--float'>io_uring</a>’
<a href='/jenkins/job/gerrit-libosmocore-build/a2=default,a3=default,a4=default,arch=arm-none-eabi,label=io_uring/' class='jenkins-table__link model-link model-link--float'>gerrit-libosmocore-build » a2=default,a3=default,a4=default,arm-none-eabi,io_uring</a> completed with result SUCCESS
<a href='/jenkins/job/gerrit-libosmocore-build/a2=default,a3=default,a4=default,arch=amd64,label=io_uring/' class='jenkins-table__link model-link model-link--float'>gerrit-libosmocore-build » a2=default,a3=default,a4=default,amd64,io_uring</a> completed with result SUCCESS
Finished: SUCCESS