Started by an SCM change Running as SYSTEM Building on the built-in node in workspace /var/jenkins_home/jobs/master-osmo-e1d/workspace [ssh-agent] Looking for ssh-agent implementation... $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-XXXXXXQB0n7B/agent.1172051 SSH_AGENT_PID=1172054 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /var/jenkins_home/jobs/master-osmo-e1d/workspace@tmp/private_key_4224956083237858688.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-osmo-e1d/workspace/.git # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://gerrit.osmocom.org/osmo-e1d # timeout=10 Fetching upstream changes from https://gerrit.osmocom.org/osmo-e1d > git --version # timeout=10 > git --version # 'git version 2.39.5' > git fetch --tags --force --progress -- https://gerrit.osmocom.org/osmo-e1d +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 0c1a3d7eddd586af9ff32dc60ba506fe8a231e92 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 0c1a3d7eddd586af9ff32dc60ba506fe8a231e92 # timeout=10 Commit message: "Avoid segfault during 'show octoi-clients' VTY command" > git rev-list --no-walk 1a807cc0100d6f537f122a385f72a84e6dc0d161 # timeout=10 Triggering master-osmo-e1d » a1=default,a2=default,a3=default,a4=default,osmocom-master Configuration master-osmo-e1d » a1=default,a2=default,a3=default,a4=default,osmocom-master is still in the queue: ‘build2-deb10build-ansible’ is offline ‘build2-deb11build-ansible’ is offline ‘gtp0-deb10fr’ doesn’t have label ‘osmocom-master’ ‘host2-deb11build-ansible’ is offline ‘lx2-raspbian11build-ansible’ doesn’t have label ‘osmocom-master’ ‘octsimtest’ doesn’t have label ‘osmocom-master’ ‘osmo-gsm-tester-prod’ doesn’t have label ‘osmocom-master’ ‘osmo-gsm-tester-rnd’ doesn’t have label ‘osmocom-master’ ‘rpi4-raspbian12build-ansible-1’ doesn’t have label ‘osmocom-master’ ‘rpi4-raspbian12build-ansible-2’ doesn’t have label ‘osmocom-master’ Configuration master-osmo-e1d » a1=default,a2=default,a3=default,a4=default,osmocom-master is still in the queue: Waiting for next available executor on ‘osmocom-master’ master-osmo-e1d » 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 1172054 killed; [ssh-agent] Stopped. Triggering a new build of Osmocom_OBS_master Finished: SUCCESS