From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [xen-4.0-testing test] 9610: regressions - FAIL
Date: Tue, 25 Oct 2011 21:47:21 +0100 [thread overview]
Message-ID: <osstest-9610-mainreport@xen.org> (raw)
flight 9610 xen-4.0-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/9610/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-amd64-xl-sedf 5 xen-boot fail REGR. vs. 9599
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-amd64-xl-pcipt-intel 8 debian-fixup fail never pass
test-amd64-i386-xl-multivcpu 15 guest-stop fail never pass
test-amd64-i386-xl 15 guest-stop fail never pass
test-i386-i386-xl 15 guest-stop fail never pass
test-amd64-amd64-xl 15 guest-stop fail never pass
test-amd64-i386-xl-credit2 14 guest-localmigrate/x10 fail blocked in 9599
test-amd64-i386-win 16 leak-check/check fail never pass
test-amd64-i386-rhel6hvm-intel 7 redhat-install fail never pass
test-amd64-i386-rhel6hvm-amd 7 redhat-install fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-amd64-amd64-win 16 leak-check/check fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-win 7 windows-install fail never pass
test-i386-i386-xl-win 7 windows-install fail never pass
test-amd64-i386-xl-win-vcpus1 7 windows-install fail never pass
version targeted for testing:
xen a5cc3b953ed9
baseline version:
xen da9f945b3db8
------------------------------------------------------------
People who touched revisions under test:
Keir Fraser <keir@xen.org>
Wei Huang <wei.huang2@amd.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 fail
test-amd64-i386-xl fail
test-i386-i386-xl fail
test-amd64-i386-rhel6hvm-amd fail
test-amd64-i386-xl-credit2 fail
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel fail
test-amd64-i386-xl-multivcpu fail
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-i386-i386-pair pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-i386-i386-pv pass
test-amd64-amd64-xl-sedf fail
test-amd64-i386-win-vcpus1 fail
test-amd64-i386-xl-win-vcpus1 fail
test-amd64-amd64-win fail
test-amd64-i386-win fail
test-i386-i386-win fail
test-amd64-amd64-xl-win fail
test-i386-i386-xl-win fail
------------------------------------------------------------
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: 21551:a5cc3b953ed9
tag: tip
user: Wei Huang <wei.huang2@amd.com>
date: Tue Oct 25 16:44:40 2011 +0100
amd xsave: Move xsave initialization code to a common place
This patch moves xsave/xrstor code to CPU common file. First of all,
it prepares xsave/xrstor support for AMD CPUs. Secondly, Xen would
crash on __context_switch() without this patch on xsave-capable AMD
CPUs. The crash was due to cpu_has_xsave reports true in domain.c
while xsave space wasn't initialized.
Signed-off-by: Wei Huang <wei.huang2@amd.com>
xen-unstable changeset: 22462:98eb4a334b77
xen-unstable date: Tue Dec 07 18:26:38 2010 +0000
changeset: 21550:da9f945b3db8
user: Keir Fraser <keir@xen.org>
date: Mon Oct 24 18:04:42 2011 +0100
Revert xen-unstable:23871:503ee256fecf
Signed-off-by: Keir Fraser <keir@xen.org>
(qemu changes not included)
reply other threads:[~2011-10-25 20:47 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-9610-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.