[Qa-jenkins-scm] Build failed in Jenkins: lvc_debian-8.4.0 #60

[jenkins at jenkins.debian.net]

See <https://jenkins.debian.net/job/lvc_debian-8.4.0/60/>

------------------------------------------
Started by user Holger Levsen
Building remotely on profitbricks-build10-amd64.debian.net (profitbricks10 amd64) in workspace <https://jenkins.debian.net/job/lvc_debian-8.4.0/ws/>
[lvc_debian-8.4.0] $ /bin/sh -xe /tmp/hudson8789346320860288535.sh
+ /srv/jenkins/bin/jenkins_master_wrapper.sh http://cdimage.debian.org/debian-cd/8.4.0/amd64/iso-cd/debian-8.4.0-amd64-netinst.iso /srv/jenkins/cucumber/features
====================================================================================

Sat May 28 14:45:37 UTC 2016 - running /srv/jenkins/bin/lvc.sh () 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/debian-cd/8.4.0/amd64/iso-cd/debian-8.4.0-amd64-netinst.iso /srv/jenkins/cucumber/features" as arguments.

====================================================================================
Sat May 28 14:45:37 UTC 2016 - start running "/srv/jenkins/bin/lvc.sh" (md5sum 886708ba4c3c59569620aeff6932f944) as "/tmp/jenkins-script-qAYZtnQb" on profitbricks-build10-amd64.

error: failed to get domain 'DebianToaster'
error: Domain not found: no domain with matching name 'DebianToaster'
Downloading http://cdimage.debian.org/debian-cd/8.4.0/amd64/iso-cd/debian-8.4.0-amd64-netinst.iso
8d52d1b7789cd5a464aae719f05299ec  /var/lib/jenkins/debian-8.4.0-amd64-netinst.iso
Debug log available at runtime at https://jenkins.debian.net/view/lvc/job//ws/results/debug.log
run_test_suite: error: 'cucumber' is missing, please install it and run again.
Usage: run_test_suite [OPTION]... [--] [CUCUMBER_ARGS]...
Sets up an appropriate environment and invokes cucumber. Note that this script
must be run from the Tails source directory root.

Options for '@product' features:
  --artifacts-base-uri URI
                     Pretend that the artifact is located at URI when printing
                     its location during a scenario failure. This is useful if
                     you intend to serve the artifacts via the web, for
                     instance.
  --capture          Captures failed scenarios into videos stored in the
                     temporary directory (see --tmpdir below) using x264
                     encoding. Requires x264.
  --capture-all      Keep videos for all scenarios, including those that
                     succeed (implies --capture).
  --pause-on-fail    On failure, pause test suite until pressing Enter. This is
                     useful for investigating the state of the VM guest to see
                     exactly why a test failed.
  --keep-snapshots   Don't ever delete any snapshots (including ones marked as
                     temporary). This can be a big time saver when debugging new
                     features.
  --retry-find       Print a warning whenever Sikuli fails to find an image
                     and allow *one* retry after pressing ENTER. This is useful
                     for updating outdated images.
  --tmpdir           Directory where various temporary files are written
                     during a test, e.g. VM snapshots and memory dumps,
                     failure screenshots, pcap files and disk images
                     (default is TMPDIR in the environment, and if unset,
                     /tmp/DebianToaster).
  --view             Shows the test session in a windows. Requires x11vnc
                     and xtightvncviewer.
  --vnc-server-only  Starts a VNC server for the test session. Requires x11vnc.
  --iso IMAGE        Test '@product' features using IMAGE.
  --old-iso IMAGE    For some '@product' features (e.g. usb_install) we need
                     an older version of Tails, which this options sets to
                     IMAGE. If none is given, it defaults to the same IMAGE
                     given by --iso, which will be good enough for most testing
                     purposes.

Note that '@source' features has no relevant options.

CUCUMBER_ARGS can be used to specify which features to be run, but also any
cucumber option, although then you must pass `--` first to let this wrapper
script know that we're done with *its* options. For debugging purposes, a
'debug' formatter has been added so pretty debugging can be enabled with
`--format debug`. You could even combine the default (pretty) formatter with
pretty debugging printed to a file with `--format pretty --format debug
--out debug.log`.

Trying to preserve last screenshot…
Sat May 28 14:46:04 UTC 2016 - /srv/jenkins/bin/lvc.sh stopped running as /tmp/jenkins-script-qAYZtnQb, which will now be removed.
/srv/jenkins/cucumber/bin/run_test_suite: line 138: XVFB_PID: unbound variable
ls: cannot access results/*.png: No such file or directory
Build step 'Execute shell' marked build as failure