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] 4699: regressions - FAIL
Date: Sat, 8 Jan 2011 17:55:13 +0000 [thread overview]
Message-ID: <osstest-4699-mainreport@xen.org> (raw)
flight 4699 xen-4.0-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/4699/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-i386-xl-multivcpu 9 guest-start fail REGR. vs. 4544
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 15 guest-stop fail never pass
test-amd64-i386-rhel6hvm-amd 7 redhat-install fail never pass
test-amd64-i386-rhel6hvm-intel 7 redhat-install fail never pass
test-amd64-i386-win 16 leak-check/check fail never pass
test-amd64-i386-xl-credit2 7 debian-install fail like 4544
test-amd64-i386-xl 15 guest-stop fail never pass
test-amd64-xcpkern-i386-rhel6hvm-amd 7 redhat-install fail never pass
test-amd64-xcpkern-i386-rhel6hvm-intel 7 redhat-install fail never pass
test-amd64-xcpkern-i386-win 16 leak-check/check fail never pass
test-amd64-xcpkern-i386-xl-credit2 15 guest-stop fail never pass
test-amd64-xcpkern-i386-xl-multivcpu 15 guest-stop fail never pass
test-amd64-xcpkern-i386-xl 15 guest-stop fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-i386-i386-xl 15 guest-stop fail never pass
test-i386-xcpkern-i386-win 16 leak-check/check fail never pass
test-i386-xcpkern-i386-xl 15 guest-stop fail never pass
version targeted for testing:
xen ee9d0e23fff7
baseline version:
xen 7f91f7c9d13d
------------------------------------------------------------
People who touched revisions under test:
Jan Beulich <jbeulich@novell.com>
Juergen Gross <juergen.gross@ts.fujitsu.com>
Keir Fraser <keir@xen.org>
------------------------------------------------------------
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 fail
test-amd64-i386-xl fail
test-i386-i386-xl fail
test-amd64-xcpkern-i386-xl fail
test-i386-xcpkern-i386-xl fail
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 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-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
------------------------------------------------------------
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: 21426:ee9d0e23fff7
tag: tip
user: Keir Fraser <keir@xen.org>
date: Fri Jan 07 13:32:36 2011 +0000
Update my email address to long-term stable address.
Signed-off-by: Keir Fraser <keir@xen.org>
xen-unstable changeset: 22675:0ab058a55c24
xen-unstable date: Fri Jan 07 13:30:04 2011 +0000
changeset: 21425:3b90a5353f20
user: Keir Fraser <keir@xen.org>
date: Thu Jan 06 19:05:06 2011 +0000
kexec: correct _domain offset info in elf-notes
The hypervisor writes some data structure infos into the elf note
section of the vmcore to enable interpretation of the xen structures
by kexec/kdump.
The info of the offset of _domain in page_info was just wrong on
non-ia64 systems.
Signed-off-by: Juergen Gross <juergen.gross@ts.fujitsu.com>
xen-unstable changeset: 22666:cb756381087c
xen-unstable date: Thu Jan 06 19:02:36 2011 +0000
changeset: 21424:8c451cdc2dca
user: Keir Fraser <keir@xen.org>
date: Thu Jan 06 18:57:28 2011 +0000
Update QEMU_TAG
changeset: 21423:7f91f7c9d13d
user: Keir Fraser <keir@xen.org>
date: Wed Jan 05 10:01:11 2011 +0000
relax vCPU pinned checks
Both writing of certain MSRs and VCPUOP_get_physid make sense also for
dynamically (perhaps temporarily) pinned vcpus.
Likely a couple of other MSR writes (MSR_K8_HWCR, MSR_AMD64_NB_CFG,
MSR_FAM10H_MMIO_CONF_BASE) would make sense to be restricted by an
is_pinned() check too, possibly also some MSR reads.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
xen-unstable changeset: 22649:39194f457534
xen-unstable date: Wed Jan 05 09:57:15 2011 +0000
(qemu changes not included)
reply other threads:[~2011-01-08 17:55 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-4699-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.