|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-4.3-testing test] 29511: regressions - trouble: blocked/broken/fail/pass
flight 29511 xen-4.3-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/29511/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-winxpsp3-vcpus1 3 host-install(3) broken REGR. vs. 28886 test-amd64-i386-xl-qemuu-debianhvm-amd64 3 host-install(3) broken REGR. vs. 28886 test-amd64-i386-xend-qemut-winxpsp3 3 host-install(3) broken REGR. vs. 28886 test-amd64-i386-xl-credit2 11 guest-saverestore fail REGR. vs. 28886 test-amd64-amd64-xl-qemut-winxpsp3 7 windows-install fail REGR. vs. 28886 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-sedf 3 host-install(3) broken REGR. vs. 28886 Tests which did not succeed, but are not blocking: test-amd64-amd64-rumpuserxen-amd64 1 build-check(1) blocked n/a test-amd64-i386-rumpuserxen-i386 1 build-check(1) blocked n/a build-i386-rumpuserxen 6 xen-build fail never pass test-amd64-i386-xl-qemuu-ovmf-amd64 7 debian-hvm-install fail never pass build-amd64-rumpuserxen 6 xen-build fail never pass test-amd64-amd64-xl-qemuu-ovmf-amd64 7 debian-hvm-install fail never pass test-amd64-i386-libvirt 9 guest-start fail never pass test-amd64-amd64-libvirt 9 guest-start fail never pass test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass test-armhf-armhf-libvirt 5 xen-boot fail never pass test-armhf-armhf-xl 5 xen-boot fail never pass test-amd64-i386-xl-win7-amd64 14 guest-stop fail never pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 14 guest-stop fail never pass test-amd64-amd64-xl-qemuu-winxpsp3 14 guest-stop fail never pass test-amd64-i386-xl-qemut-winxpsp3-vcpus1 14 guest-stop fail never pass test-amd64-i386-xl-qemut-win7-amd64 14 guest-stop fail never pass test-amd64-amd64-xl-qemuu-win7-amd64 14 guest-stop fail never pass test-amd64-amd64-xl-win7-amd64 14 guest-stop fail never pass test-amd64-amd64-xl-qemut-win7-amd64 14 guest-stop fail never pass test-amd64-i386-xl-qemuu-win7-amd64 14 guest-stop fail never pass test-amd64-i386-xend-winxpsp3 17 leak-check/check fail never pass test-amd64-amd64-xl-winxpsp3 14 guest-stop fail never pass version targeted for testing: xen 1a9452adc6795f4cc2e37d7472371993eedf2f69 baseline version: xen 83c1512e488637286c9a0cf4f58ed85094c15ac2 ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Aravindh Puthiyaparambil <aravindp@xxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Juergen Gross <jgross@xxxxxxxx> Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Stefan Bader <stefan.bader@xxxxxxxxxxxxx> Tamas K Lengyel <tamas.lengyel@xxxxxxxxxxxx> Yang Zhang <yang.z.zhang@xxxxxxxxx> ------------------------------------------------------------ jobs: build-amd64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass build-amd64-rumpuserxen fail build-i386-rumpuserxen fail test-amd64-amd64-xl pass test-armhf-armhf-xl fail test-amd64-i386-xl pass test-amd64-i386-rhel6hvm-amd pass test-amd64-i386-qemut-rhel6hvm-amd pass test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-amd64-xl-qemut-debianhvm-amd64 pass test-amd64-i386-xl-qemut-debianhvm-amd64 pass test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-xl-qemuu-debianhvm-amd64 broken test-amd64-i386-freebsd10-amd64 pass test-amd64-amd64-xl-qemuu-ovmf-amd64 fail test-amd64-i386-xl-qemuu-ovmf-amd64 fail test-amd64-amd64-rumpuserxen-amd64 blocked test-amd64-amd64-xl-qemut-win7-amd64 fail test-amd64-i386-xl-qemut-win7-amd64 fail test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-i386-xl-qemuu-win7-amd64 fail test-amd64-amd64-xl-win7-amd64 fail test-amd64-i386-xl-win7-amd64 fail test-amd64-i386-xl-credit2 fail test-amd64-i386-freebsd10-i386 pass test-amd64-i386-rumpuserxen-i386 blocked test-amd64-amd64-xl-pcipt-intel fail test-amd64-i386-rhel6hvm-intel pass test-amd64-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-amd64-libvirt fail test-armhf-armhf-libvirt fail test-amd64-i386-libvirt fail test-amd64-i386-xl-multivcpu pass test-amd64-amd64-pair pass test-amd64-i386-pair pass test-amd64-amd64-xl-sedf-pin pass test-amd64-amd64-pv pass test-amd64-i386-pv pass test-amd64-amd64-xl-sedf broken test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail test-amd64-i386-xl-winxpsp3-vcpus1 broken test-amd64-i386-xend-qemut-winxpsp3 broken test-amd64-amd64-xl-qemut-winxpsp3 fail test-amd64-amd64-xl-qemuu-winxpsp3 fail test-amd64-i386-xend-winxpsp3 fail test-amd64-amd64-xl-winxpsp3 fail ------------------------------------------------------------ sg-report-flight on osstest.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. ------------------------------------------------------------ commit 1a9452adc6795f4cc2e37d7472371993eedf2f69 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Mon Jul 28 15:06:47 2014 +0200 x86/mem_event: prevent underflow of vcpu pause counts Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Tested-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Reviewed-by: Andres Lagar-Cavilla <andres@xxxxxxxxxxxxxxxx> Tested-by: Aravindh Puthiyaparambil <aravindp@xxxxxxxxx> master commit: 868d9b99b39c53dc1f6ae9bfd7b148c206fd7240 master date: 2014-07-23 18:08:04 +0200 commit 60400ce54cbc61365ff665946f0ba767c1694203 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Mon Jul 28 15:06:09 2014 +0200 x86/mem_event: validate the response vcpu_id before acting on it Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Tim Deegan <tim@xxxxxxx> Reviewed-by: Andres Lagar-Cavilla <andres@xxxxxxxxxxxxxxxx> Tested-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> master commit: ee75480b3c8856db9ef1aa45418f35ec0d78989d master date: 2014-07-23 18:07:11 +0200 commit afb3cb30be6d3116660e1db145e0859993295161 Author: Tamas K Lengyel <tamas.lengyel@xxxxxxxxxxxx> Date: Mon Jul 28 15:05:25 2014 +0200 x86/mem_event: fix regression affecting CR0 memory events This is a patch repairing a regression in code previously functional in 4.1.x. It appears that, during some refactoring work, call to hvm_memory_event_cr0 was lost. This function was originally called in mov_to_cr() of vmx.c, but the commit http://xenbits.xen.org/hg/xen-unstable.hg/rev/1276926e3795 abstracted the original code into generic functions up a level in hvm.c, dropping the call in the process. The same issue affected the CR3 and CR4 events, which were fixed in patch http://xenbits.xensource.com/hg/xen-unstable.hg/rev/7ab899e46347. Signed-off-by: Tamas K Lengyel <tamas.lengyel@xxxxxxxxxxxx> Reviewed-by: Tim Deegan <tim@xxxxxxx> master commit: 5d570c1d0274cac3b333ef378af3325b3b69905e master date: 2014-07-23 18:05:11 +0200 commit 49f8aa2e272ea7802930e60d486163ab74b291a9 Author: Juergen Gross <jgross@xxxxxxxx> Date: Mon Jul 28 15:04:43 2014 +0200 avoid crash when doing shutdown with active cpupools When shutting down the machine while there are cpus in a cpupool other than Pool-0 a crash is triggered due to cpupool handling rejecting offlining the non-boot cpus in other cpupools. It is easy to detect this case and allow offlining those cpus. Reported-by: Stefan Bader <stefan.bader@xxxxxxxxxxxxx> Signed-off-by: Juergen Gross <jgross@xxxxxxxx> Tested-by: Stefan Bader <stefan.bader@xxxxxxxxxxxxx> master commit: 05377dede434c746e6708f055858378d20f619db master date: 2014-07-23 18:03:19 +0200 commit 8ea3fb47af98efa84a26aaede772abf140102323 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Mon Jul 28 15:03:42 2014 +0200 properly reference count DOMCTL_{,un}pausedomain hypercalls For safety reasons, c/s 6ae2df93c27 "mem_access: Add helper API to setup ring and enable mem_access" has to pause the domain while it performs a set of operations. However without properly reference counted hypercalls, xc_mem_event_enable() now unconditionally unpauses a previously paused domain. To prevent toolstack software running wild, there is an arbitrary limit of 255 on the toolstack pause count. This is high enough for several components of the toolstack to safely use, but prevents over/underflow of d->pause_count. The previous domain_{,un}pause_by_systemcontroller() functions are updated to return an error code. domain_pause_by_systemcontroller() is modified to have a common stub and take a pause_fn pointer, allowing for both sync and nosync domain pauses. domain_pause_for_debugger() has a hand-rolled nosync pause replaced with the new domain_pause_by_systemcontroller_nosync(), and has its variables shuffled slightly to avoid rereading current multiple times. Suggested-by: Don Slutz <dslutz@xxxxxxxxxxx> Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> With a couple of formatting adjustments: Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> x86/gdbsx: invert preconditions for XEN_DOMCTL_gdbsx_{,un}pausevcpu hypercalls c/s 3eb1c708ab "properly reference count DOMCTL_{,un}pausedomain hypercalls" accidentally inverted the use of d->controller_pause_count. Revert back to how it was originally, i.e. the XEN_DOMCTL_gdbsx_{,un}pausevcpu hypercalls are only valid for a domain already paused by the system controller. Reported-by: Jan Beulich <jbeulich@xxxxxxxx> Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 3eb1c708ab0fe1067a436498a684907afa14dacf master date: 2014-07-03 16:51:13 +0200 master commit: 680d79f10bb70691a9ae3b4a6a8b669e0f2837f6 master date: 2014-07-25 11:53:31 +0200 commit c3b1d10be6ebe4ff53d961c4507381f0aefb7f2a Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Mon Jul 28 15:02:25 2014 +0200 VT-d/ATS: correct and clean up dev_invalidate_iotlb() While this was intended to only do cleanup (replace the two bogus "ret |= " constructs, and a simple formatting correction), this now also - fixes the bit manipulations for size_order > 0 a) correct an off-by-one in the use of size_order for shifting (till now double the requested size got invalidated) b) in fact setting bit 12 and up if necessary (without which too small a region might have got invalidated) c) making them capable of dealing with regions of 4Gb size and up - corrects the return value handling, such that a later iteration's success won't clear an earlier iteration's error indication - uses PCI_BDF2() instead of open coding it - bail immediately on bad passed in invalidation type, rather than repeatedly printing the same message for each ATS-capable device, at once also no longer hiding that failure from the caller Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Yang Zhang <yang.z.zhang@xxxxxxxxx> master commit: fd33987ba27607c3cc7da258cf1d86d21beeb735 master date: 2014-06-30 15:57:40 +0200 ======================================== _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |