|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable test] 58832: regressions - FAIL
flight 58832 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/58832/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-win7-amd64 9 windows-install fail REGR. vs. 58821 Regressions which are regarded as allowable (not blocking): test-armhf-armhf-libvirt-xsm 6 xen-boot fail REGR. vs. 58821 test-armhf-armhf-xl-sedf 6 xen-boot fail REGR. vs. 58821 test-amd64-i386-libvirt-xsm 11 guest-start fail like 58821 test-amd64-i386-libvirt 11 guest-start fail like 58821 test-amd64-amd64-libvirt-xsm 11 guest-start fail like 58821 test-amd64-amd64-libvirt 11 guest-start fail like 58821 test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail like 58821 test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 58821 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pvh-intel 11 guest-start fail never pass test-amd64-amd64-xl-pvh-amd 11 guest-start fail never pass test-armhf-armhf-xl-arndale 12 migrate-support-check fail never pass test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass test-armhf-armhf-xl-xsm 12 migrate-support-check fail never pass test-armhf-armhf-xl 12 migrate-support-check fail never pass test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail never pass test-armhf-armhf-xl-credit2 12 migrate-support-check fail never pass test-armhf-armhf-xl-cubietruck 12 migrate-support-check fail never pass test-armhf-armhf-xl-sedf-pin 12 migrate-support-check fail never pass test-armhf-armhf-libvirt 12 migrate-support-check fail never pass version targeted for testing: xen 6501e9cc6a9473561f4b4bf3ee5583cc08f9e86d baseline version: xen e76ff6c156906b515c2a4300a81c95886ece5d5f ------------------------------------------------------------ People who touched revisions under test: David Vrabel <david.vrabel@xxxxxxxxxx> Don Slutz <dslutz@xxxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Juergen Gross <jgross@xxxxxxxx> ------------------------------------------------------------ jobs: build-amd64-xsm pass build-armhf-xsm pass build-i386-xsm pass build-amd64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-oldkern pass build-i386-oldkern pass build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass build-amd64-rumpuserxen pass build-i386-rumpuserxen pass test-amd64-amd64-xl pass test-armhf-armhf-xl pass test-amd64-i386-xl pass test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemut-debianhvm-amd64-xsm pass test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm pass test-amd64-amd64-libvirt-xsm fail test-armhf-armhf-libvirt-xsm fail test-amd64-i386-libvirt-xsm fail test-amd64-amd64-xl-xsm pass test-armhf-armhf-xl-xsm pass test-amd64-i386-xl-xsm pass test-amd64-amd64-xl-pvh-amd fail 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 pass test-amd64-i386-freebsd10-amd64 pass test-amd64-amd64-xl-qemuu-ovmf-amd64 pass test-amd64-i386-xl-qemuu-ovmf-amd64 pass test-amd64-amd64-rumpuserxen-amd64 pass 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-armhf-armhf-xl-arndale pass test-amd64-amd64-xl-credit2 pass test-armhf-armhf-xl-credit2 pass test-armhf-armhf-xl-cubietruck pass test-amd64-i386-freebsd10-i386 pass test-amd64-i386-rumpuserxen-i386 pass test-amd64-amd64-xl-pvh-intel fail test-amd64-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-amd64-libvirt fail test-armhf-armhf-libvirt pass test-amd64-i386-libvirt fail test-amd64-amd64-xl-multivcpu pass test-armhf-armhf-xl-multivcpu pass test-amd64-amd64-pair pass test-amd64-i386-pair pass test-amd64-amd64-xl-sedf-pin pass test-armhf-armhf-xl-sedf-pin pass test-amd64-amd64-xl-sedf pass test-armhf-armhf-xl-sedf fail test-amd64-i386-xl-qemut-winxpsp3-vcpus1 pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 pass test-amd64-amd64-xl-qemut-winxpsp3 pass test-amd64-i386-xl-qemut-winxpsp3 pass test-amd64-amd64-xl-qemuu-winxpsp3 pass test-amd64-i386-xl-qemuu-winxpsp3 pass ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/logs/logs images: /home/logs/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit 6501e9cc6a9473561f4b4bf3ee5583cc08f9e86d Author: Juergen Gross <jgross@xxxxxxxx> Date: Mon Jun 22 11:41:01 2015 +0200 update comments regarding pv-domain memory layout The comments describing the initial pv-domain memory layout are not complete. They do not mention the pages with console info and xenstore data. Add this information to the comments. Signed-off-by: Juergen Gross <jgross@xxxxxxxx> commit 2abed01bf44e03dac3083e382d8c869ab3c19eb8 Author: Don Slutz <dslutz@xxxxxxxxxxx> Date: Mon Jun 22 11:40:28 2015 +0200 gdbsx_guestmemio: allow it to check domain gdbsx_guest_mem_io() does not get d passed, it expects to handle the domain lookup itself. Specifically, the caller of XEN_DOMCTL_gdbsx_guestmemio is expected to use DOMID_IDLE to interact with the hypervisor, rather than a domain, which doesn't interact well with with the domain rcu lock. Signed-off-by: Don Slutz <dslutz@xxxxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit b58214a24231a1f2a7e09ae9cc3014eff752918b Author: David Vrabel <david.vrabel@xxxxxxxxxx> Date: Mon Jun 22 11:39:46 2015 +0200 evtchn: pad struct evtchn to 64 bytes The number of struct evtchn in a page must be a power of two. Under some workloads performance is improved slightly by padding struct evtchn to 64 bytes (a typical cache line size), thus putting the fewer per-channel locks into each cache line. This does not decrease the number of struct evtchn's per-page. Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> commit de6acb78bf0e137cbe5b72cee4a35ca018d759cc Author: David Vrabel <david.vrabel@xxxxxxxxxx> Date: Mon Jun 22 11:39:03 2015 +0200 evtchn: use a per-event channel lock for sending events When sending an event, use a new per-event channel lock to safely validate the event channel state. This new lock must be held when changing event channel state. Note that the event channel lock must also be held when changing state from ECS_FREE or it will race with a concurrent get_free_port() call. To avoid having to take the remote event channel locks when sending to an interdomain event channel, the local and remote channel locks are both held when binding or closing an interdomain event channel. This significantly increases the number of events that can be sent from multiple VCPUs. But struct evtchn increases in size, reducing the number that fit into a single page to 64 (instead of 128). Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit a753f0e53ff973a8a066e86c1cb3d6dd5c68d59f Author: David Vrabel <david.vrabel@xxxxxxxxxx> Date: Mon Jun 22 11:38:01 2015 +0200 evtchn: defer freeing struct evtchn's until evtchn_destroy_final() notify_via_xen_event_channel() and free_xen_event_channel() had to check if the domain was dying because they may be called while the domain is being destroyed and the struct evtchn's are being freed. By deferring the freeing of the struct evtchn's until all references to the domain are dropped, these functions can rely on the channel state being present and valid. Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx> commit b399386bcdb9d458f5647476a06fe86f5968d87e Author: David Vrabel <david.vrabel@xxxxxxxxxx> Date: Mon Jun 22 11:36:17 2015 +0200 evtchn: clear xen_consumer when clearing state Freeing a xen event channel would clear xen_consumer before clearing the channel state, leaving a window where the channel is in a funny state (still bound but no consumer). Move the clear of xen_consumer into free_evtchn() where the state is also cleared. Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx> Ditch the pointless evtchn_close() wrapper around __evtchn_close() (renaming the latter) as well as some bogus casts of function results to void. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> commit e722f1de2c82af870ba1caeb4fa9db45de53f4c7 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Mon Jun 22 11:34:57 2015 +0200 x86/HVM: EOI handling function adjustments The vector parameters are more usefully u8 right away. This is particularly important for the vioapic_update_EOI() invocation from vioapic_write() (which luckily is only a latent issue, as VIOAPIC_VERSION_ID is still hard coded to 0x11 right now). But it at once allows simplifying VMX's EXIT_REASON_EOI_INDUCED handling (the kind of pointless helper function should have been static anyway; not being use for anything else, it gets removed altogether). Plus vlapic_handle_EOI() (now renamed for that purpose) can be used as the tail of vlapic_EOI_set() instead of duplicating that code. Finally replace a stray current->domain use in vlapic_handle_EOI(). Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> (qemu changes not included) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |