[Qa-jenkins-scm] Build failed in Jenkins: lvc_debian-testing-daily #83

Sat Jun 25 09:09:19 UTC 2016

See <https://jenkins.debian.net/job/lvc_debian-testing-daily/83/>

------------------------------------------
Started by timer
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/hudson4717455463560724070.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
declare -x BUILD_DISPLAY_NAME="#83"
declare -x BUILD_ID="83"
declare -x BUILD_NUMBER="83"
declare -x BUILD_TAG="jenkins-lvc_debian-testing-daily-83"
declare -x BUILD_URL="https://jenkins.debian.net/job/lvc_debian-testing-daily/83/"
declare -x EXECUTOR_NUMBER="3"
declare -x HOME="/var/lib/jenkins"
declare -x HUDSON_COOKIE="ad248a6a-dc3d-411c-8a25-ccfd04711c9c"
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_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 SHELL="/bin/bash"
declare -x SHLVL="2"
declare -x SLAVEJAR_URL="https://jenkins.debian.net//jnlpJars/slave.jar"
declare -x TERM="xterm"
declare -x USER="jenkins"
declare -x WORKSPACE="<https://jenkins.debian.net/job/lvc_debian-testing-daily/ws/">
declare -x XDG_SESSION_COOKIE="9ccc5118b39c03788401bbe2501b9f12-1466610260.710308-1583807185"
declare -x XDG_SESSION_ID="16412"
debug begin
declare -x HOME="/var/lib/jenkins"
declare -x LANG="en_US.UTF-8"
declare -x LOGNAME="jenkins"
declare -x MAIL="/var/mail/jenkins"
declare -x OLDPWD
declare -x PATH="/usr/local/bin:/usr/bin:/bin:/usr/games"
declare -x PWD="/var/lib/jenkins"
declare -x SHELL="/bin/bash"
declare -x SHLVL="2"
declare -x SSH_CLIENT="78.137.96.196 41335 22"
declare -x SSH_CONNECTION="78.137.96.196 41335 85.184.249.68 22"
declare -x SSH_ORIGINAL_COMMAND="lvc_debian-testing-daily 3 PU_GIT_BRANCH= http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso /srv/jenkins/cucumber/features --tags ~@broken"
declare -x USER="jenkins"
declare -x XDG_RUNTIME_DIR="/run/user/106"
declare -x XDG_SESSION_ID="9201"
debug end
====================================================================================

Sat Jun 25 08:55:11 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" as arguments.

====================================================================================
Sat Jun 25 08:55:11 UTC 2016 - start running "/srv/jenkins/bin/lvc.sh" (md5sum a354f3b9d136f38012c4f0e38071c9a2) as "/tmp/jenkins-script-Ku4EbnnG" 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 libvirt-qemu libvirt-qemu 318767104 Jun 25 00:55 /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...
2f4cbf8f302a5f2ab4fa24b7bbf6c91e  /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:122
    When I start the computer                                         # /srv/jenkins/cucumber/features/step_definitions/common_steps.rb:197
    Then I should see a <login> Login prompt                          # /srv/jenkins/cucumber/features/step_definitions/common_steps.rb:554

    Examples: 
      | install_ui | target_ui | login |
      |OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000dff00000, 9961472, 0) failed; error='Cannot allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 9961472 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /var/lib/jenkins/hs_err_pid28521.log
Domain snapshot boot-d-i-gui-to-tasksel deleted

Domain snapshot disk-for-d-i deleted

Trying to preserve last screenshot…
ls: cannot access /var/lib/jenkins/jobs/lvc_debian-testing-daily/workspace/results/*.png: No such file or directory
Sat Jun 25 09:11:31 UTC 2016 - /srv/jenkins/bin/lvc.sh stopped running as /tmp/jenkins-script-Ku4EbnnG, which will now be removed.
Build step 'Execute shell' marked build as failure