[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable-smoke test] 63320: trouble: broken/pass
flight 63320 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/63320/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-debianhvm-i386 3 host-install(3) broken REGR. vs. 63260 Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-xl 12 migrate-support-check fail never pass test-armhf-armhf-xl 13 saverestore-support-check fail never pass version targeted for testing: xen d8ba3a9e444c6943199130eea32904bc245a6d27 baseline version: xen cd84a2baadd4a5767d2568b1c01b055328cc84db Last test of basis 63260 2015-10-23 14:00:55 Z 3 days Testing same since 63320 2015-10-26 14:01:22 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Dario Faggioli <dario.faggioli@xxxxxxxxxx> George Dunlap <george.dunlap@xxxxxxxxxx> Ian Campbell <ian.campbell@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Julien Grall <julien.grall@xxxxxxxxxx> jobs: build-amd64 pass build-armhf pass build-amd64-libvirt pass test-armhf-armhf-xl pass test-amd64-amd64-xl-qemuu-debianhvm-i386 broken test-amd64-amd64-libvirt 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 Explanation of these reports, and of osstest in general, is at http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary broken-step test-amd64-amd64-xl-qemuu-debianhvm-i386 host-install(3) Not pushing. ------------------------------------------------------------ commit d8ba3a9e444c6943199130eea32904bc245a6d27 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Mon Oct 26 14:02:30 2015 +0100 x86: remove assumptions about the layout of x86_capabilities Future work will rearange it, invalidating these assumptions. No functional change. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 7729eed1a51b417c029a32d1e6b94eb0751d1643 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Mon Oct 26 14:01:50 2015 +0100 x86: helpers for cpu feature manipulation Expose them to assembly code, and replace open-coded versions. No functional change. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 69176a4b9c27796bb4cde1e13f28f5eace425400 Author: Julien Grall <julien.grall@xxxxxxxxxx> Date: Mon Oct 26 13:58:35 2015 +0100 x86/mm: pod: use the correct memory flags for alloc_domheap_page{,s} The last parameter of alloc_domheap_page{s,} contain the memory flags and not the order of the allocation. Use 0 for the call in p2m_pod_set_cache_target as it was before 1069d63c5ef2510d08b83b2171af660e5bb18c63 "x86/mm/p2m: use defines for page sizes". Note that PAGE_ORDER_4K is also equal to 0 so the behavior stays the same. For the call in p2m_pod_offline_or_broken_replace we want to allocate the new page on the same numa node as the previous page. So retrieve the numa node and pass it in the memory flags. Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx> Tested-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Acked-by: George Dunlap <george.dunlap@xxxxxxxxxx> commit e896ad9a9164a432538789fa2993a1084fd0a387 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Mon Oct 26 13:56:39 2015 +0100 arm: don't build core parking code It's wired up on x86 only. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Ian Campbell <ian.campbell@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 |