|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable test] 25348: regressions - FAIL
flight 25348 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/25348/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-winxpsp3 4 xen-install fail REGR. vs. 25347 Regressions which are regarded as allowable (not blocking): test-armhf-armhf-xl 9 guest-start fail like 25347 test-amd64-amd64-xl-sedf-pin 15 guest-localmigrate/x10 fail like 25347 test-amd64-i386-xl-qemuu-win7-amd64 7 windows-install fail like 25341 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 14 guest-stop fail never pass test-amd64-i386-xend-qemut-winxpsp3 17 leak-check/check fail never pass test-amd64-i386-xend-winxpsp3 17 leak-check/check 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-i386-xl-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-win7-amd64 14 guest-stop fail never pass test-amd64-amd64-xl-qemut-winxpsp3 14 guest-stop fail never pass test-amd64-i386-xl-qemut-winxpsp3-vcpus1 14 guest-stop fail never pass test-amd64-i386-xl-win7-amd64 14 guest-stop fail never pass test-amd64-amd64-xl-qemut-win7-amd64 14 guest-stop fail never pass version targeted for testing: xen 7e9009891688202a7ffb63761b94e9ae0a53795a baseline version: xen 79de2d31f1ff8910231b7ec15519405953e6571a ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Keir Fraser <keir@xxxxxxx> Xiantao Zhang <xiantao.zhang@xxxxxxxxx> ------------------------------------------------------------ jobs: build-amd64-xend pass build-i386-xend pass build-amd64 pass build-armhf pass build-i386 pass build-amd64-oldkern pass build-i386-oldkern pass build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass 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-i386-freebsd10-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-amd64-amd64-xl-win7-amd64 fail test-amd64-i386-xl-win7-amd64 fail test-amd64-i386-xl-credit2 pass test-amd64-i386-freebsd10-i386 pass 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-i386-xl-multivcpu pass test-amd64-amd64-pair pass test-amd64-i386-pair pass test-amd64-amd64-xl-sedf-pin fail test-amd64-amd64-pv pass test-amd64-i386-pv pass test-amd64-amd64-xl-sedf pass test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail test-amd64-i386-xl-winxpsp3-vcpus1 fail test-amd64-i386-xend-qemut-winxpsp3 fail 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 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. ------------------------------------------------------------ commit 7e9009891688202a7ffb63761b94e9ae0a53795a Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Mar 4 11:03:13 2014 +0100 include: parallelize compat/xlat.h generation Splitting this up into pieces signficantly speeds up building on multi- CPU systems when making use of make's -j option. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Keir Fraser <keir@xxxxxxx> commit 3cdb47bcf2d33b5c6b49b25c4cb7b85de89e5cc4 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Mar 4 11:01:57 2014 +0100 correctly use gcc's -x option In Linux the improper use was found to cause problems with certain distributed build environments. Even if not directly affecting us, be on the safe side. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Keir Fraser <keir@xxxxxxx> commit 7acf827b951b4e8501a777676ddf050d200103a4 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Mar 4 11:00:26 2014 +0100 x86/ACPI: also print address space for PM1x fields At least one vendor is in the process of making systems available where these live in MMIO, not in I/O port space. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Keir Fraser <keir@xxxxxxx> commit 658a736299f7c91b7db1e1c12b01cc8b8f232fa8 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Mar 4 10:59:44 2014 +0100 x86/AMD: re-use function wide variables in init_amd() Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Keir Fraser <keir@xxxxxxx> commit 8db22866dbbcabf30ad6e3814489c730b53d1cf4 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Mar 4 10:58:19 2014 +0100 x86: don't propagate acpi_skip_timer_override do Dom0 It's unclear why c/s 4850:923dd9975981 added this - Dom0 isn't controlling the timer interrupt, and hence has no need to know. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Keir Fraser <keir@xxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 58bebfdb790c5639d28d5e1b5fd49a3352c5fc25 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Tue Mar 4 10:55:56 2014 +0100 x86/time: avoid redundant this_cpu() this_cpu() makes use of RELOC_HIDE() to prevent unsafe optimisations, forcing a recalculation of the per-cpu data area. Don't use it needlessly. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit e72747e2d1d67818d56eacbc9a8423c4259b64ca Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Mar 4 10:54:21 2014 +0100 x86/time: cleanup Eliminate effectively unused variables mistakenly left in place by 9539:08aede767c63 ("Rename update_dom_time() to update_vcpu_system_time()"). Drop the pointless casts. Use SECONDS() instead of open coding it. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Keir Fraser <keir@xxxxxxx> commit 9ef5aa944a6a0df7f5938983043c7e46f158bbc6 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Mar 4 10:52:20 2014 +0100 IOMMU: generalize and correct softirq processing during Dom0 device setup c/s 21039:95f5a4ce8f24 ("VT-d: reduce default verbosity") having put a call to process_pending_softirqs() in VT-d's domain_context_mapping() was wrong in two ways: For one we shouldn't be doing this when setting up a device during DomU assignment. And then - I didn't check whether that was the case already back then - we shouldn't call that function with the pcidevs_lock (or in fact any spin lock) held. Move the "preemption" into generic code, at once dealing with further actual (too much output elsewhere - particularly on systems with very many host bridge like devices - having been observed to still cause the watchdog to trigger when enabled) and potential (other IOMMU code may also end up being too verbose) issues. Do the "preemption" once per device actually being set up when in verbose mode, and once per bus otherwise. Note that dropping pcidevs_lock around the process_pending_softirqs() invocation is specifically not a problem here: We're in an __init function and aren't racing with potential additions/removals of PCI devices. Not acquiring the lock in setup_dom0_pci_devices() otoh is not an option, as there are too many places that assert the lock being held. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Xiantao Zhang <xiantao.zhang@xxxxxxxxx> (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 |