xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: xen.org <Ian.Jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [libvirt test] 29664: regressions - FAIL
Date: Sun, 10 Aug 2014 20:12:05 +0100	[thread overview]
Message-ID: <osstest-29664-mainreport@xen.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2733 bytes --]

flight 29664 libvirt real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/29664/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-armhf                   5 xen-build                 fail REGR. vs. 29585

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-libvirt      1 build-check(1)               blocked  n/a
 build-armhf-libvirt           1 build-check(1)               blocked  n/a
 test-amd64-i386-libvirt       9 guest-start                  fail   never pass
 test-amd64-amd64-libvirt      9 guest-start                  fail   never pass

version targeted for testing:
 libvirt              954538720dc576af08c95ed02858acb2975e9ed5
baseline version:
 libvirt              be3cbecd0ef0c5b2d711d1451261cd8ad4e0228e

------------------------------------------------------------
People who touched revisions under test:
  Daniel Veillard <veillard@redhat.com>
  Eric Blake <eblake@redhat.com>
  Jianwei Hu <jiahu@redhat.com>
  John Ferlan <jferlan@redhat.com>
  Ján Tomko <jtomko@redhat.com>
  Kiarie Kahurani <davidkiarie4@gmail.com>
  Laine Stump <laine@laine.org>
  Martin Kletzander <mkletzan@redhat.com>
  Michal Privoznik <mprivozn@redhat.com>
  Peter Krempa <pkrempa@redhat.com>
  Prerna Saxena <prerna@linux.vnet.ibm.com>
  Wang Rui <moon.wangrui@huawei.com>
------------------------------------------------------------

jobs:
 build-amd64                                                  pass
 build-armhf                                                  fail
 build-i386                                                   pass
 build-amd64-libvirt                                          pass
 build-armhf-libvirt                                          blocked
 build-i386-libvirt                                           pass
 build-amd64-pvops                                            pass
 build-armhf-pvops                                            pass
 build-i386-pvops                                             pass
 test-amd64-amd64-libvirt                                     fail
 test-armhf-armhf-libvirt                                     blocked
 test-amd64-i386-libvirt                                      fail


------------------------------------------------------------
sg-report-flight on osstest.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images

Logs, config files, etc. are available at
    http://www.chiark.greenend.org.uk/~xensrcts/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Not pushing.

(No revision log; it would be 592 lines long.)


[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

                 reply	other threads:[~2014-08-10 19:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=osstest-29664-mainreport@xen.org \
    --to=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).