Console Output

Started by upstream project "master-libosmocore" build number 4142
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-trx/workspace
[ssh-agent] Looking for ssh-agent implementation...
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXc74iHJ/agent.3673567
SSH_AGENT_PID=3673570
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /var/jenkins_home/jobs/master-osmo-trx/workspace@tmp/private_key_1435141339171105754.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-trx/workspace/.git # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://gerrit.osmocom.org/osmo-trx # timeout=10
Fetching upstream changes from https://gerrit.osmocom.org/osmo-trx
 > git --version # timeout=10
 > git --version # 'git version 2.39.5'
 > git fetch --tags --force --progress -- https://gerrit.osmocom.org/osmo-trx +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 3642b5956ccc124cd02f8b08661a36db63c9d2b4 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 3642b5956ccc124cd02f8b08661a36db63c9d2b4 # timeout=10
Commit message: "contrib/jenkins: remove broken chroot + qemu code"
 > git rev-list --no-walk 3642b5956ccc124cd02f8b08661a36db63c9d2b4 # timeout=10
 > git remote # timeout=10
 > git submodule init # timeout=10
 > git submodule sync # timeout=10
 > git config --get remote.origin.url # timeout=10
 > git submodule init # timeout=10
 > git config -f .gitmodules --get-regexp ^submodule\.(.+)\.url # timeout=10
 > git config --get submodule.osmocom-bb.url # timeout=10
 > git config -f .gitmodules --get submodule.osmocom-bb.path # timeout=10
 > git submodule update --init --recursive osmocom-bb # timeout=10
Triggering master-osmo-trx » --with-sse,0,a3=default,a4=default,osmocom-master
Triggering master-osmo-trx » --without-sse,1,a3=default,a4=default,osmocom-master
Triggering master-osmo-trx » --with-neon,0,a3=default,a4=default,raspbian
Triggering master-osmo-trx » --with-neon-vfpv4,0,a3=default,a4=default,raspbian
Configuration master-osmo-trx » --with-sse,0,a3=default,a4=default,osmocom-master is still in the queue: Waiting for next available executor on ‘osmocom-master’
master-osmo-trx » --with-sse,0,a3=default,a4=default,osmocom-master completed with result SUCCESS
master-osmo-trx » --without-sse,1,a3=default,a4=default,osmocom-master completed with result SUCCESS
master-osmo-trx » --with-neon,0,a3=default,a4=default,raspbian completed with result SUCCESS
master-osmo-trx » --with-neon-vfpv4,0,a3=default,a4=default,raspbian completed with result SUCCESS
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 3673570 killed;
[ssh-agent] Stopped.
Triggering a new build of Osmocom_OBS_master
Triggering a new build of osmo-gsm-tester_build-osmo-trx
Finished: SUCCESS