From: xen.org <Ian.Jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [linux-next test] 32192: regressions - FAIL
Date: Wed, 10 Dec 2014 15:42:09 +0000 [thread overview]
Message-ID: <osstest-32192-mainreport@xen.org> (raw)
flight 32192 linux-next real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/32192/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-libvirt 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-rumpuserxen-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-libvirt 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-xl-credit2 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-xl-multivcpu 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-xl 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-rumpuserxen-i386 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-qemuu-rhel6hvm-amd 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-qemut-rhel6hvm-amd 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-rhel6hvm-amd 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-freebsd10-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-qemut-rhel6hvm-intel 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-freebsd10-i386 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-xl-qemut-win7-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-xl-qemut-winxpsp3 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-qemuu-rhel6hvm-intel 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-rhel6hvm-intel 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-xl-qemut-debianhvm-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-xl-qemuu-debianhvm-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-xl-qemuu-ovmf-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-pair 8 xen-boot/dst_host fail REGR. vs. 32141
test-amd64-amd64-pair 7 xen-boot/src_host fail REGR. vs. 32141
test-amd64-amd64-xl-qemut-win7-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-xl-qemut-debianhvm-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-xl-qemuu-debianhvm-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-xl-qemuu-ovmf-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-pair 8 xen-boot/dst_host fail REGR. vs. 32141
test-amd64-i386-pair 7 xen-boot/src_host fail REGR. vs. 32141
test-amd64-i386-xl-qemuu-win7-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-xl-winxpsp3 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-xl-qemuu-winxpsp3 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-xl-win7-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-xl-winxpsp3-vcpus1 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-xl-qemuu-winxpsp3 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-xl-qemuu-win7-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-xl-winxpsp3 5 xen-boot fail REGR. vs. 32141
test-amd64-i386-xl-win7-amd64 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-xl-qemut-winxpsp3 5 xen-boot fail REGR. vs. 32141
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-pcipt-intel 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-xl-sedf-pin 5 xen-boot fail REGR. vs. 32141
test-amd64-amd64-xl-sedf 5 xen-boot fail REGR. vs. 32141
test-armhf-armhf-xl 12 guest-start.2 fail blocked in 32141
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 9 guest-start fail never pass
test-armhf-armhf-xl 10 migrate-support-check fail never pass
version targeted for testing:
linux cf12164be498180dc466ef97194ca7755ea39f3b
baseline version:
linux 19b022572b9e0fa8ce5490db888714ecb2b1293e
jobs:
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-libvirt pass
build-armhf-libvirt pass
build-i386-libvirt pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
build-amd64-rumpuserxen pass
build-i386-rumpuserxen pass
test-amd64-amd64-xl fail
test-armhf-armhf-xl fail
test-amd64-i386-xl fail
test-amd64-i386-rhel6hvm-amd fail
test-amd64-i386-qemut-rhel6hvm-amd fail
test-amd64-i386-qemuu-rhel6hvm-amd fail
test-amd64-amd64-xl-qemut-debianhvm-amd64 fail
test-amd64-i386-xl-qemut-debianhvm-amd64 fail
test-amd64-amd64-xl-qemuu-debianhvm-amd64 fail
test-amd64-i386-xl-qemuu-debianhvm-amd64 fail
test-amd64-i386-freebsd10-amd64 fail
test-amd64-amd64-xl-qemuu-ovmf-amd64 fail
test-amd64-i386-xl-qemuu-ovmf-amd64 fail
test-amd64-amd64-rumpuserxen-amd64 fail
test-amd64-amd64-xl-qemut-win7-amd64 fail
test-amd64-i386-xl-qemut-win7-amd64 fail
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 fail
test-amd64-amd64-xl-win7-amd64 fail
test-amd64-i386-xl-win7-amd64 fail
test-amd64-i386-xl-credit2 fail
test-amd64-i386-freebsd10-i386 fail
test-amd64-i386-rumpuserxen-i386 fail
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel fail
test-amd64-i386-qemut-rhel6hvm-intel fail
test-amd64-i386-qemuu-rhel6hvm-intel fail
test-amd64-amd64-libvirt fail
test-armhf-armhf-libvirt fail
test-amd64-i386-libvirt fail
test-amd64-i386-xl-multivcpu fail
test-amd64-amd64-pair fail
test-amd64-i386-pair fail
test-amd64-amd64-xl-sedf-pin fail
test-amd64-amd64-xl-sedf fail
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail
test-amd64-i386-xl-winxpsp3-vcpus1 fail
test-amd64-amd64-xl-qemut-winxpsp3 fail
test-amd64-i386-xl-qemut-winxpsp3 fail
test-amd64-amd64-xl-qemuu-winxpsp3 fail
test-amd64-i386-xl-qemuu-winxpsp3 fail
test-amd64-amd64-xl-winxpsp3 fail
test-amd64-i386-xl-winxpsp3 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
Push not applicable.
reply other threads:[~2014-12-10 15: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-32192-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.