All of lore.kernel.org
 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] 32064: regressions - FAIL
Date: Wed, 3 Dec 2014 21:42:25 +0000	[thread overview]
Message-ID: <osstest-32064-mainreport@xen.org> (raw)

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

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

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-i386-libvirt            5 libvirt-build             fail REGR. vs. 32005
 build-amd64-libvirt           5 libvirt-build             fail REGR. vs. 32005
 build-armhf-libvirt           5 libvirt-build             fail REGR. vs. 32005

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

version targeted for testing:
 libvirt              86a15a258283850ec5563e2a66bf389aa2dfa318
baseline version:
 libvirt              ff018e686a8a412255bc34d3dc558a1bcf74fac5

------------------------------------------------------------
People who touched revisions under test:
  Daniel Hansel <daniel.hansel@linux.vnet.ibm.com>
  Dmitry Guryanov <dguryanov@parallels.com>
  John Ferlan <jferlan@redhat.com>
  Ján Tomko <jtomko@redhat.com>
  Laine Stump <laine@laine.org>
  Martin Kletzander <mkletzan@redhat.com>
  Michal Privoznik <mprivozn@redhat.com>
  Pavel Hrdina <phrdina@redhat.com>
  Wang Rui <moon.wangrui@huawei.com>
------------------------------------------------------------

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


------------------------------------------------------------
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 333 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-12-03 21:42 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-32064-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.