[Qa-jenkins-scm] Build failed in Jenkins: lvc_debian-testing-daily #483
jenkins at jenkins.debian.net
jenkins at jenkins.debian.net
Sat Nov 5 17:27:38 UTC 2016
https://jenkins.debian.net/job/lvc_debian-testing-daily/483/------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on profitbricks-build10-amd64.debian.net (profitbricks10 lvc amd64) in workspace <https://jenkins.debian.net/job/lvc_debian-testing-daily/ws/>
[lvc_debian-testing-daily] $ /bin/sh -xe /tmp/hudson7741404450422882718.sh
+ /srv/jenkins/bin/jenkins_master_wrapper.sh http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso /srv/jenkins/cucumber/features --tags ~@broken --tags ~@trivial --tags ~@preseed
declare -x BUILD_CAUSE="TIMERTRIGGER"
declare -x BUILD_CAUSE_TIMERTRIGGER="true"
declare -x BUILD_DISPLAY_NAME="#483"
declare -x BUILD_ID="483"
declare -x BUILD_NUMBER="483"
declare -x BUILD_TAG="jenkins-lvc_debian-testing-daily-483"
declare -x BUILD_URL="https://jenkins.debian.net/job/lvc_debian-testing-daily/483/"
declare -x EXECUTOR_NUMBER="0"
declare -x HOME="/var/lib/jenkins"
declare -x HUDSON_COOKIE="34146f36-e41e-4494-8c70-c18db198fa23"
declare -x HUDSON_HOME="/var/lib/jenkins"
declare -x HUDSON_SERVER_COOKIE="662be26f1caf0950"
declare -x HUDSON_URL="https://jenkins.debian.net/"
declare -x JENKINS_HOME="/var/lib/jenkins"
declare -x JENKINS_SERVER_COOKIE="662be26f1caf0950"
declare -x JENKINS_URL="https://jenkins.debian.net/"
declare -x JOB_BASE_NAME="lvc_debian-testing-daily"
declare -x JOB_NAME="lvc_debian-testing-daily"
declare -x JOB_URL="https://jenkins.debian.net/job/lvc_debian-testing-daily/"
declare -x LANG="en_GB.UTF-8"
declare -x LANGUAGE="en_GB:en"
declare -x LOGNAME="jenkins"
declare -x MAIL="/var/mail/jenkins"
declare -x NODE_LABELS="amd64 lvc profitbricks-build10-amd64.debian.net profitbricks10"
declare -x NODE_NAME="profitbricks-build10-amd64.debian.net"
declare -x OLDPWD
declare -x PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
declare -x PWD="<https://jenkins.debian.net/job/lvc_debian-testing-daily/ws/">
declare -x ROOT_BUILD_CAUSE="TIMERTRIGGER"
declare -x ROOT_BUILD_CAUSE_TIMERTRIGGER="true"
declare -x SHELL="/bin/bash"
declare -x SHLVL="2"
declare -x SLAVEJAR_URL="https://jenkins.debian.net//jnlpJars/slave.jar"
declare -x TERM="linux"
declare -x USER="jenkins"
declare -x WORKSPACE="/srv/jenkins/pseudo-hosts/profitbricks-build10-amd64"
declare -x XDG_SESSION_COOKIE="9ccc5118b39c03788401bbe2501b9f12-1478361087.778199-206887279"
====================================================================================
Sat Nov 5 16:52:01 UTC 2016 - running /srv/jenkins/bin/lvc.sh (lvc_debian-testing-daily) on profitbricks-build10-amd64 now.
To learn to understand this, clone git.debian.org/git/qa/jenkins.debian.net.git
and then have a look at the files README, INSTALL, CONTRIBUTING and maybe TODO.
This invocation of this script, which is located in bin/lvc.sh,
has been called using "http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso /srv/jenkins/cucumber/features --tags ~@broken --tags ~@trivial --tags ~@preseed" as arguments.
Please send technical feedback about jenkins to qa-jenkins-dev at lists.alioth.debian.org,
feedback about specific jobs result should go to their respective lists and/or the BTS.
====================================================================================
Sat Nov 5 16:52:01 UTC 2016 - start running "/srv/jenkins/bin/lvc.sh" (md5sum 447f48c7b3f2875c9482c088707eab91) as "/tmp/jenkins-script-odfsthU8" on profitbricks-build10-amd64.
Downloading http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
-rw-r--r-- 1 jenkins jenkins 313524224 Nov 5 08:53 /var/lib/jenkins/jobs/lvc_debian-testing-daily/workspace/debian-testing-amd64-netinst.iso
File exists, will only re-download if a newer one is available...
be2e2b9b065d4450386af774ca9e3e4e /var/lib/jenkins/jobs/lvc_debian-testing-daily/workspace/debian-testing-amd64-netinst.iso
Debug log available at runtime at https://jenkins.debian.net/view/lvc/job/lvc_debian-testing-daily/ws/results/debug.log
Virtual X framebuffer started on display :0
VNC server running on: localhost:5900
[info] Sikuli vision engine loaded.
@product
Feature: Doing variations on d-i installs
As a normal user
I should be able to install Debian
Scenario Outline: Install Debian, and boot to a login prompt # /srv/jenkins/cucumber/features/install.feature:6
Given I install a <target_ui> Debian system, in <install_ui> mode # /srv/jenkins/cucumber/features/step_definitions/snapshots.rb:103
When I start the computer # /srv/jenkins/cucumber/features/step_definitions/common_steps.rb:204
Then I should see a <login> Login prompt # /srv/jenkins/cucumber/features/step_definitions/common_steps.rb:563
Examples:
| install_ui | target_ui | login |
| gui | minimal | VT |
| gui | LXDE | LXDE |
| gui | XFCE | XFCE |
| gui | KDE | KDE |
Artifacts directory: /var/lib/jenkins/jobs/lvc_debian-testing-daily/workspace/results
4 scenarios (4 passed)
12 steps (12 passed)
15m11.342s
Sat Nov 5 17:07:36 UTC 2016 - /srv/jenkins/bin/lvc.sh stopped running as /tmp/jenkins-script-odfsthU8, which will now be removed.
Sat 5 Nov 17:07:36 UTC 2016 - retrieving artifacts.
+ mkdir -p <https://jenkins.debian.net/job/lvc_debian-testing-daily/ws/results>
+ rsync -r --delete -v -e 'ssh -o '\''Batchmode = yes'\'' -p 22' profitbricks-build10-amd64.debian.net:/var/lib/jenkins/jobs/lvc_debian-testing-daily/workspace/results/ <https://jenkins.debian.net/job/lvc_debian-testing-daily/ws/results/>
receiving incremental file list
Timeout, server profitbricks-build10-amd64.debian.net not responding.
rsync: connection unexpectedly closed (195 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [receiver=3.1.1]
rsync: connection unexpectedly closed (203 bytes received so far) [generator]
rsync error: unexplained error (code 255) at io.c(226) [generator=3.1.1]
Build step 'Execute shell' marked build as failure
More information about the Qa-jenkins-scm
mailing list