| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] [xen-4.0-testing test] 4634: regressions - FAIL
flight 4634 xen-4.0-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/4634/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-xcpkern-i386-pair 16 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 15 guest-stop 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-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 3b90a5353f20
baseline version:
xen 7f91f7c9d13d
------------------------------------------------------------
People who touched revisions under test:
Jan Beulich <jbeulich@xxxxxxxxxx>
Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
------------------------------------------------------------
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 fail
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: 21425:3b90a5353f20
tag: tip
user: Keir Fraser <keir@xxxxxxx>
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@xxxxxxxxxxxxxx>
xen-unstable changeset: 22666:cb756381087c
xen-unstable date: Thu Jan 06 19:02:36 2011 +0000
changeset: 21424:8c451cdc2dca
user: Keir Fraser <keir@xxxxxxx>
date: Thu Jan 06 18:57:28 2011 +0000
Update QEMU_TAG
changeset: 21423:7f91f7c9d13d
user: Keir Fraser <keir@xxxxxxx>
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@xxxxxxxxxx>
xen-unstable changeset: 22649:39194f457534
xen-unstable date: Wed Jan 05 09:57:15 2011 +0000
(qemu changes not included)
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-devel] [xen-4.0-testing test] 4634: regressions - FAIL,
xen . org <=
|
|
|
| |
|
Home