Started by timer Building remotely on build1-debian9-lxc (linux_amd64_debian9) in workspace /home/osmocom-build/jenkins/workspace/ttcn3-nitb-sysinfo [ttcn3-nitb-sysinfo] $ /bin/sh -xe /tmp/jenkins5694458766861697026.sh + env JENKINS_HOME=/usr/local/jenkins MAIL=/var/mail/osmocom-build SSH_CLIENT=192.168.122.1 56262 22 USER=osmocom-build RUN_CHANGES_DISPLAY_URL=http://jenkins.osmocom.org/jenkins/job/ttcn3-nitb-sysinfo/109/display/redirect?page=changes NODE_LABELS=build1-debian9-lxc linux_amd64_debian9 HUDSON_URL=http://jenkins.osmocom.org/jenkins/ SHLVL=1 OLDPWD=/home/osmocom-build HOME=/home/osmocom-build BUILD_URL=http://jenkins.osmocom.org/jenkins/job/ttcn3-nitb-sysinfo/109/ HUDSON_COOKIE=b5e618db-25ce-4f16-9b87-ff38da1382a1 JENKINS_SERVER_COOKIE=8cd9590adb8bfe87 WORKSPACE=/home/osmocom-build/jenkins/workspace/ttcn3-nitb-sysinfo LOGNAME=osmocom-build NODE_NAME=build1-debian9-lxc _=/usr/bin/java EXECUTOR_NUMBER=0 XDG_SESSION_ID=1005 BUILD_DISPLAY_NAME=#109 HUDSON_HOME=/usr/local/jenkins JOB_BASE_NAME=ttcn3-nitb-sysinfo PATH=/usr/local/bin:/usr/bin:/bin:/usr/games:/home/osmocom-build/bin BUILD_ID=109 XDG_RUNTIME_DIR=/run/user/1000 BUILD_TAG=jenkins-ttcn3-nitb-sysinfo-109 LANG=en_US.UTF-8 JENKINS_URL=http://jenkins.osmocom.org/jenkins/ JOB_URL=http://jenkins.osmocom.org/jenkins/job/ttcn3-nitb-sysinfo/ BUILD_NUMBER=109 PARALLEL_MAKE=-j 3 SHELL=/bin/bash RUN_DISPLAY_URL=http://jenkins.osmocom.org/jenkins/job/ttcn3-nitb-sysinfo/109/display/redirect HUDSON_SERVER_COOKIE=8cd9590adb8bfe87 JOB_DISPLAY_URL=http://jenkins.osmocom.org/jenkins/job/ttcn3-nitb-sysinfo/display/redirect JOB_NAME=ttcn3-nitb-sysinfo PWD=/home/osmocom-build/jenkins/workspace/ttcn3-nitb-sysinfo SSH_CONNECTION=192.168.122.1 56262 192.168.122.224 22 MAKE=make + OLDPWD=/home/osmocom-build/jenkins/workspace/ttcn3-nitb-sysinfo + DIR=/home/osmocom-build/jenkins/docker-playground + cd /home/osmocom-build/jenkins/docker-playground + git fetch + git checkout -f -B master origin/master Reset branch 'master' Branch master set up to track remote branch master from origin. Your branch is up-to-date with 'origin/master'. + cd /home/osmocom-build/jenkins/docker-playground/osmo-nitb-master + make docker build -t docker.io/osmocom-build/osmo-nitb-master:latest . Sending build context to Docker daemon 12.29kB Step 1/14 : FROM laforge/debian-jessie-build ---> 80385047baea Step 2/14 : MAINTAINER Harald Welte <laforge@gnumonks.org> ---> Using cache ---> 1372d15076ce Step 3/14 : COPY Release.key /tmp/Release.key ---> Using cache ---> 7c8827de5720 Step 4/14 : RUN apt-key add /tmp/Release.key && rm /tmp/Release.key && echo "deb http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/ ./" > /etc/apt/sources.list.d/osmocom-nightly.list ---> Using cache ---> 4aa34ab677b0 Step 5/14 : RUN apt-get update && apt-get install -y --no-install-recommends telnet libosmocore-dev libosmo-abis-dev libosmo-netif-dev libosmo-sccp-dev libsmpp34-dev libgtp-dev && apt-get clean ---> Using cache ---> 3ab96e043ac0 Step 6/14 : WORKDIR /tmp ---> Using cache ---> 90ae0a60838d Step 7/14 : RUN git clone git://git.osmocom.org/openbsc.git ---> Using cache ---> 249082cf419e Step 8/14 : ADD http://git.osmocom.org/openbsc/patch /tmp/commit-openbsc ---> Using cache ---> a6ec05188ac1 Step 9/14 : RUN cd openbsc/openbsc && git fetch && git checkout -f -B master origin/master && autoreconf -fi && ./configure --enable-nat --enable-osmo-bsc --enable-smpp && make -j8 install && ldconfig ---> Using cache ---> 489f300515a8 Step 10/14 : VOLUME /data ---> Using cache ---> f3458665a793 Step 11/14 : COPY openbsc.cfg /data/openbsc.cfg ---> Using cache ---> 8eeda3da162d Step 12/14 : WORKDIR /data ---> Using cache ---> b8aad56f4c7e Step 13/14 : CMD /usr/local/bin/osmo-nitb ---> Using cache ---> d49abc7f5028 Step 14/14 : EXPOSE 3002/tcp 3003/tcp 4242/tcp 2775/tcp 4249/tcp ---> Using cache ---> 86be715fd5c5 Successfully built 86be715fd5c5 Successfully tagged osmocom-build/osmo-nitb-master:latest + cd /home/osmocom-build/jenkins/docker-playground/osmo-bts-master + make docker build -t docker.io/osmocom-build/osmo-bts-master:latest . Sending build context to Docker daemon 9.216kB Step 1/13 : FROM laforge/debian-jessie-build ---> 80385047baea Step 2/13 : MAINTAINER Harald Welte <laforge@gnumonks.org> ---> Using cache ---> 1372d15076ce Step 3/13 : COPY Release.key /tmp/Release.key ---> Using cache ---> 7c8827de5720 Step 4/13 : RUN apt-key add /tmp/Release.key && rm /tmp/Release.key && echo "deb http://download.opensuse.org/repositories/network:/osmocom:/nightly/Debian_8.0/ ./" > /etc/apt/sources.list.d/osmocom-nightly.list ---> Using cache ---> 4aa34ab677b0 Step 5/13 : RUN apt-get update && apt-get install -y --no-install-recommends telnet libosmocore-dev libosmo-abis-dev libosmo-netif-dev libosmo-sccp-dev libsmpp34-dev libgtp-dev && apt-get clean ---> Using cache ---> 3ab96e043ac0 Step 6/13 : WORKDIR /tmp ---> Using cache ---> 90ae0a60838d Step 7/13 : RUN git clone git://git.osmocom.org/osmo-bts.git ---> Using cache ---> bb42d3aab864 Step 8/13 : ADD http://git.osmocom.org/osmo-bts/patch /tmp/commit-osmo-bts ADD failed: Got HTTP status code >= 400: 504 Gateway Time-out ../make/Makefile:43: recipe for target 'docker-build' failed make: *** [docker-build] Error 1 Build step 'Execute shell' marked build as failure Recording test results ERROR: Step ‘Publish JUnit test result report’ failed: Test reports were found but none of them are new. Did tests run? For example, /home/osmocom-build/jenkins/workspace/ttcn3-nitb-sysinfo/logs/ttcn3-nitb-sysinfo/junit-xml-19.log is 23 hr old Sending e-mails to: laforge@gnumonks.org Finished: FAILURE