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] 7001: regressions - trouble: blocked/broken/fail/pass
Date: Mon, 9 May 2011 18:50:58 +0100 [thread overview]
Message-ID: <osstest-7001-mainreport@xen.org> (raw)
flight 7001 xen-4.0-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/7001/
Regressions :-(
Tests which did not succeed and are blocking:
build-i386-oldkern 2 host-install(2) broken
build-i386 2 host-install(2) broken
test-amd64-i386-pair 6 xen-install/dst_host fail REGR. vs. 6931
test-amd64-i386-pair 5 xen-install/src_host fail REGR. vs. 6931
test-amd64-i386-pv 4 xen-install fail REGR. vs. 6931
test-amd64-i386-rhel6hvm-amd 4 xen-install fail REGR. vs. 6931
test-amd64-i386-rhel6hvm-intel 4 xen-install fail REGR. vs. 6931
test-amd64-i386-win-vcpus1 4 xen-install fail REGR. vs. 6931
test-amd64-i386-win 4 xen-install fail REGR. vs. 6931
test-amd64-i386-xl-multivcpu 4 xen-install fail REGR. vs. 6931
test-amd64-i386-xl-win-vcpus1 4 xen-install fail REGR. vs. 6931
test-amd64-i386-xl 4 xen-install fail REGR. vs. 6931
test-amd64-xcpkern-i386-pair 6 xen-install/dst_host fail REGR. vs. 6931
test-amd64-xcpkern-i386-pair 5 xen-install/src_host fail REGR. vs. 6931
test-amd64-xcpkern-i386-pv 4 xen-install fail REGR. vs. 6931
test-amd64-xcpkern-i386-rhel6hvm-amd 4 xen-install fail REGR. vs. 6931
test-amd64-xcpkern-i386-rhel6hvm-intel 4 xen-install fail REGR. vs. 6931
test-amd64-xcpkern-i386-win 4 xen-install fail REGR. vs. 6931
test-amd64-xcpkern-i386-xl-multivcpu 4 xen-install fail REGR. vs. 6931
test-amd64-xcpkern-i386-xl-win 4 xen-install fail REGR. vs. 6931
test-amd64-xcpkern-i386-xl 4 xen-install fail REGR. vs. 6931
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 7 windows-install fail never pass
test-amd64-amd64-xl 15 guest-stop fail never pass
test-amd64-i386-xl-credit2 4 xen-install fail REGR. vs. 6931
test-amd64-xcpkern-i386-xl-credit2 4 xen-install fail REGR. vs. 6931
test-i386-i386-pair 1 xen-build-check(1) blocked n/a
test-i386-i386-pv 1 xen-build-check(1) blocked n/a
test-i386-i386-win 1 xen-build-check(1) blocked n/a
test-i386-i386-xl-win 1 xen-build-check(1) blocked n/a
test-i386-i386-xl 1 xen-build-check(1) blocked n/a
test-i386-xcpkern-i386-pair 1 xen-build-check(1) blocked n/a
test-i386-xcpkern-i386-pv 1 xen-build-check(1) blocked n/a
test-i386-xcpkern-i386-win 1 xen-build-check(1) blocked n/a
test-i386-xcpkern-i386-xl 1 xen-build-check(1) blocked n/a
version targeted for testing:
xen e91977e7ab3a
baseline version:
xen 50066fb241dd
------------------------------------------------------------
People who touched revisions under test:
Daniel Kiper <dkiper@net-space.pl>
Keir Fraser <keir@xen.org>
------------------------------------------------------------
jobs:
build-i386-xcpkern pass
build-amd64 pass
build-i386 broken
build-amd64-oldkern pass
build-i386-oldkern broken
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl fail
test-amd64-i386-xl fail
test-i386-i386-xl blocked
test-amd64-xcpkern-i386-xl fail
test-i386-xcpkern-i386-xl blocked
test-amd64-i386-rhel6hvm-amd fail
test-amd64-xcpkern-i386-rhel6hvm-amd fail
test-amd64-i386-xl-credit2 fail
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 fail
test-amd64-xcpkern-i386-xl-multivcpu fail
test-amd64-amd64-pair pass
test-amd64-i386-pair fail
test-i386-i386-pair blocked
test-amd64-xcpkern-i386-pair fail
test-i386-xcpkern-i386-pair blocked
test-amd64-amd64-pv pass
test-amd64-i386-pv fail
test-i386-i386-pv blocked
test-amd64-xcpkern-i386-pv fail
test-i386-xcpkern-i386-pv blocked
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 blocked
test-amd64-xcpkern-i386-win fail
test-i386-xcpkern-i386-win blocked
test-amd64-amd64-xl-win fail
test-i386-i386-xl-win blocked
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: 21481:e91977e7ab3a
tag: tip
user: Keir Fraser <keir@xen.org>
date: Mon May 09 12:20:24 2011 +0100
x86: Clean up smp_call_function handling.
We don't need so many communication fields between caller and
handler.
Signed-off-by: Keir Fraser <keir@xen.org>
xen-unstable changeset: 23285:a7ac0a0170b0
xen-unstable date: Sun May 01 09:32:48 2011 +0100
changeset: 21480:50066fb241dd
user: Daniel Kiper <dkiper@net-space.pl>
date: Wed Apr 27 13:31:04 2011 +0100
pv-grub: Fix for incorrect dom->p2m_host[] list initialization
Introduction of Linux Kernel git commit
ceefccc93932b920a8ec6f35f596db05202a12fe (x86: default
CONFIG_PHYSICAL_START and CONFIG_PHYSICAL_ALIGN to 16 MB) revealed
deeply hidden bug in pv-grub. During kernel load stage dom->p2m_host[]
list has been incorrectly initialized.
At the beginning of kernel load stage dom->p2m_host[] list is
populated with current PFN->MFN layout. Later during memory allocation
(memory is allocated page by page in kexec_allocate()) page order is
changed to establish linear layout in new domain. It is done by
exchanging subsequent MFNs with newly allocated MFNs. dom->p2m_host[]
list is indexed by currently requested PFN (it is incremented from 0)
and PFN of newly allocated paged. If PFN of newly allocated page is
less than currently requested PFN then earlier allocated MFN is
overwritten which leads to domain crash later. This patch corrects
that issue. If PFN of newly allocated page is less then currently
requested PFN then relevant PFN/MFN pair is properly calculated and
usual exchange occurs later.
Signed-off-by: Daniel Kiper <dkiper@net-space.pl>
Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
xen-unstable changeset: 23249:83fe79c0225f
xen-unstable date: Wed Apr 27 13:29:14 2011 +0100
(qemu changes not included)
reply other threads:[~2011-05-09 17:50 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-7001-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).