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] 6321: regressions - FAIL
Date: Sun, 6 Mar 2011 03:40:06 +0000 [thread overview]
Message-ID: <osstest-6321-mainreport@xen.org> (raw)
flight 6321 xen-4.1-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/6321/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-i386-rhel6hvm-intel 7 redhat-install fail REGR. vs. 6306
test-amd64-xcpkern-i386-xl-credit2 13 guest-localmigrate.2 fail REGR. vs. 6306
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-win 13 guest-stop fail never pass
test-amd64-i386-rhel6hvm-amd 8 guest-saverestore fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-win 16 leak-check/check fail never pass
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass
test-amd64-xcpkern-i386-rhel6hvm-amd 8 guest-saverestore fail never pass
test-amd64-xcpkern-i386-rhel6hvm-intel 8 guest-saverestore fail never pass
test-amd64-xcpkern-i386-win 16 leak-check/check fail never pass
test-amd64-xcpkern-i386-xl-win 13 guest-stop fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-i386-i386-xl-win 13 guest-stop fail never pass
test-i386-xcpkern-i386-win 16 leak-check/check fail never pass
version targeted for testing:
xen 0f9f2248127e
baseline version:
xen 6241fa0ad1a9
------------------------------------------------------------
People who touched revisions under test:
Keir Fraser <keir@xen.org>
Liu, Jinsong <jinsong.liu@intel.com>
------------------------------------------------------------
jobs:
build-i386-xcpkern pass
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 pass
test-amd64-xcpkern-i386-xl pass
test-i386-xcpkern-i386-xl pass
test-amd64-i386-rhel6hvm-amd fail
test-amd64-xcpkern-i386-rhel6hvm-amd fail
test-amd64-i386-xl-credit2 pass
test-amd64-xcpkern-i386-xl-credit2 fail
test-amd64-i386-rhel6hvm-intel fail
test-amd64-xcpkern-i386-rhel6hvm-intel fail
test-amd64-i386-xl-multivcpu pass
test-amd64-xcpkern-i386-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-i386-i386-pair pass
test-amd64-xcpkern-i386-pair pass
test-i386-xcpkern-i386-pair pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-i386-i386-pv pass
test-amd64-xcpkern-i386-pv pass
test-i386-xcpkern-i386-pv pass
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-xcpkern-i386-win fail
test-i386-xcpkern-i386-win fail
test-amd64-amd64-xl-win fail
test-i386-i386-xl-win fail
test-amd64-xcpkern-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: 22980:0f9f2248127e
tag: tip
user: Keir Fraser <keir@xen.org>
date: Sat Mar 05 16:05:52 2011 +0000
x86: Cache read of cpu_state in __cpu_die() for subsequent BUG_ON check.
Otherwise compiler may re-read cpu_state for the BUG_ON and see a
modified value causing erroneous BUG.
Signed-off-by: Keir Fraser <keir@xen.org>
Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com>
xen-unstable changeset: 22977:bbc03993d31f
xen-unstable date: Sat Mar 05 16:02:33 2011 +0000
changeset: 22979:9d4cdf7d70b9
user: Keir Fraser <keir@xen.org>
date: Sat Mar 05 11:37:42 2011 +0000
x86: On CPU offline, fix master waiting for slave to be fully dead.
On two back-to-back CPU offline operations, on second offline the
cpu_state var will be CPU_STATE_DEAD from the first offline. Hence
__cpu_die() will incorrectly not wait for the second slave to fully
die and set cpu_state itself.
The fix is to set cpu_state to a new value, CPU_STATE_DYING, earlier
during CPU offline, before __cpu_die() starts to execute.
Original diagnosis and patch by Liu, Jinsong <jinsong.liu@intel.com>
Signed-off-by: Keir Fraser <keir@xen.org>
xen-unstable changeset: 22975:d3d29df8f082
xen-unstable date: Sat Mar 05 11:34:41 2011 +0000
changeset: 22978:51e74954aa8f
user: Keir Fraser <keir@xen.org>
date: Sat Mar 05 11:35:29 2011 +0000
preempt: Disable preemption support for 4.1.
Preemption support is not needed for 4.1 branch as synchronous yield
(via waitqueues) is not used. Furthermore there are still some
unbalanced rcu_lock/unlock usages on some code paths and the stricter
requirements of the preemption subsystem can cause us to BUG out on
them.
Signed-off-by: Keir Fraser <keir@xen.org>
changeset: 22977:6af8e01d3e4a
user: Keir Fraser <keir@xen.org>
date: Sat Mar 05 11:25:30 2011 +0000
credit2: Revert debugging patch 22965:9dfd7ffcd76c for release.
Signed-off-by: Keir Fraser <keir@xen.org>
changeset: 22976:ddc214f425d3
user: Keir Fraser <keir@xen.org>
date: Fri Mar 04 21:46:06 2011 +0000
Set debug=n by default.
Signed-off-by: Keir Fraser <keir@xen.org>
changeset: 22975:a3cd99f9606d
user: Keir Fraser <keir@xen.org>
date: Fri Mar 04 21:45:25 2011 +0000
Update QEMU_REMOTE to qemu-xen-4.1-testing.git
changeset: 22974:0662bff7dabb
user: Ian Jackson <Ian.Jackson@eu.citrix.com>
date: Fri Mar 04 17:33:32 2011 +0000
Added signature for changeset 6241fa0ad1a9
changeset: 22973:ba8cc8846eb6
user: Ian Jackson <Ian.Jackson@eu.citrix.com>
date: Fri Mar 04 17:33:18 2011 +0000
Added tag 4.1.0-branched for changeset 6241fa0ad1a9
changeset: 22972:6241fa0ad1a9
tag: 4.1.0-branched
parent: 22971:3db8805c4995
parent: 22966:de49500f344a
user: Ian Jackson <Ian.Jackson@eu.citrix.com>
date: Thu Mar 03 18:52:09 2011 +0000
Merge
(qemu changes not included)
reply other threads:[~2011-03-06 3: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-6321-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.