From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [xen-4.1-testing test] 13680: regressions - trouble: broken/fail/pass
Date: Wed, 12 Sep 2012 06:40:05 +0100 [thread overview]
Message-ID: <osstest-13680-mainreport@xen.org> (raw)
flight 13680 xen-4.1-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/13680/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-i386-i386-pv 9 guest-start fail REGR. vs. 13657
test-i386-i386-xl-winxpsp3 3 host-install(3) broken REGR. vs. 13657
test-amd64-i386-xl-win7-amd64 3 host-install(3) broken REGR. vs. 13657
test-i386-i386-xl 3 host-install(3) broken REGR. vs. 13657
test-i386-i386-xl-win 3 host-install(3) broken REGR. vs. 13657
test-i386-i386-win 3 host-install(3) broken REGR. vs. 13657
test-amd64-i386-xl-win-vcpus1 3 host-install(3) broken REGR. vs. 13657
test-amd64-i386-xl-winxpsp3-vcpus1 3 host-install(3) broken REGR. vs. 13657
test-amd64-i386-win 3 host-install(3) broken REGR. vs. 13657
test-amd64-i386-win-vcpus1 3 host-install(3) broken REGR. vs. 13657
test-amd64-amd64-xl-qemuu-winxpsp3 3 host-install(3) broken REGR. vs. 13657
test-amd64-i386-qemuu-rhel6hvm-intel 3 host-install(3) broken REGR. vs. 13657
test-amd64-amd64-xl-win7-amd64 3 host-install(3) broken REGR. vs. 13657
test-amd64-i386-qemuu-rhel6hvm-amd 3 host-install(3) broken REGR. vs. 13657
test-amd64-i386-rhel6hvm-amd 3 host-install(3) broken REGR. vs. 13657
test-i386-i386-xl-qemuu-winxpsp3 3 host-install(3) broken REGR. vs. 13657
test-amd64-amd64-xl-winxpsp3 3 host-install(3) broken REGR. vs. 13657
test-amd64-i386-pair 3 host-install/src_host(3) broken REGR. vs. 13657
test-amd64-i386-pair 4 host-install/dst_host(4) broken REGR. vs. 13657
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-pcipt-intel 8 debian-fixup fail like 13657
test-amd64-amd64-xl-sedf 5 xen-boot fail like 13657
Tests which did not succeed, but are not blocking:
test-amd64-i386-rhel6hvm-intel 11 leak-check/check fail never pass
test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-win 13 guest-stop fail never pass
version targeted for testing:
xen 9be1175d2ac3
baseline version:
xen 3e4782f17f5c
------------------------------------------------------------
People who touched revisions under test:
Ian Jackson <ian.jackson@eu.citrix.com>
------------------------------------------------------------
jobs:
build-amd64 pass
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-amd64-i386-xl pass
test-i386-i386-xl broken
test-amd64-i386-rhel6hvm-amd broken
test-amd64-i386-qemuu-rhel6hvm-amd broken
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-amd64-xl-win7-amd64 broken
test-amd64-i386-xl-win7-amd64 broken
test-amd64-i386-xl-credit2 pass
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel fail
test-amd64-i386-qemuu-rhel6hvm-intel broken
test-amd64-i386-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair broken
test-i386-i386-pair pass
test-amd64-amd64-xl-sedf-pin pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-i386-i386-pv fail
test-amd64-amd64-xl-sedf fail
test-amd64-i386-win-vcpus1 broken
test-amd64-i386-xl-win-vcpus1 broken
test-amd64-i386-xl-winxpsp3-vcpus1 broken
test-amd64-amd64-win fail
test-amd64-i386-win broken
test-i386-i386-win broken
test-amd64-amd64-xl-win fail
test-i386-i386-xl-win broken
test-amd64-amd64-xl-qemuu-winxpsp3 broken
test-i386-i386-xl-qemuu-winxpsp3 broken
test-amd64-i386-xend-winxpsp3 fail
test-amd64-amd64-xl-winxpsp3 broken
test-i386-i386-xl-winxpsp3 broken
------------------------------------------------------------
sg-report-flight on woking.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.
------------------------------------------------------------
changeset: 23354:9be1175d2ac3
tag: tip
user: Ian Jackson <Ian.Jackson@eu.citrix.com>
date: Tue Sep 11 14:31:12 2012 +0100
QEMU_TAG update
changeset: 23353:3e4782f17f5c
user: Ian Jackson <Ian.Jackson@eu.citrix.com>
date: Wed Sep 05 12:40:10 2012 +0100
QEMU_TAG update (XSA-17 / CVE-2012-3515)
========================================
commit d7d453f51459b591faa96d1c123b5bfff7c5b6b6
Author: Ian Jackson <ian.jackson@eu.citrix.com>
Date: Thu Sep 6 17:05:30 2012 +0100
Disable qemu monitor by default. The qemu monitor is an overly
powerful feature which must be protected from untrusted (guest)
administrators.
Neither xl nor xend expect qemu to produce this monitor unless it is
explicitly requested.
This is a security problem, XSA-19. Previously it was CVE-2007-0998
in Red Hat but we haven't dealt with it in upstream. We hope to have
a new CVE for it here but we don't have one yet.
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
(cherry picked from commit bacc0d302445c75f18f4c826750fb5853b60e7ca)
reply other threads:[~2012-09-12 5:40 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-13680-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).