[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable-smoke test] 93908: regressions - FAIL
flight 93908 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/93908/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 5 xen-build fail REGR. vs. 93623 Tests which did not succeed, but are not blocking: build-amd64-libvirt 1 build-check(1) blocked n/a test-amd64-amd64-libvirt 1 build-check(1) blocked n/a test-amd64-amd64-xl-qemuu-debianhvm-i386 1 build-check(1) blocked n/a 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 4084fee7a3204bf8ccf7d993dea09186e4e7dd48 baseline version: xen f8c66c2ad2efdb281e4ebf15bf329d73c4f02ce7 Last test of basis 93623 2016-05-06 17:00:49 Z 2 days Testing same since 93908 2016-05-09 12:01:07 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: George Dunlap <george.dunlap@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Juergen Gross <jgross@xxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> jobs: build-amd64 fail build-armhf pass build-amd64-libvirt blocked test-armhf-armhf-xl pass test-amd64-amd64-xl-qemuu-debianhvm-i386 blocked test-amd64-amd64-libvirt blocked ------------------------------------------------------------ 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 Not pushing. ------------------------------------------------------------ commit 4084fee7a3204bf8ccf7d993dea09186e4e7dd48 Author: Juergen Gross <jgross@xxxxxxxx> Date: Mon May 9 10:29:26 2016 +0200 doc: document that Domain-0 can't be migrated across cpupools Domain-0 is always member of Pool-0 (or, to be precise: of the cpuppol with cpupool-id 0). Document this in the xl man page. Signed-off-by: Juergen Gross <jgross@xxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> Release-acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> commit 6b08872519cba35073882db2e9a54ad00bac1c57 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Mon May 9 13:21:38 2016 +0200 MAINTAINERS: put docs/man/ under tool stack Right now there's only tool stack related documentation there. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: George Dunlap <george.dunlap@xxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> commit 94a6187794b1ef4f5d35ff746699f588831818f2 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Mon May 9 13:21:06 2016 +0200 IOMMU: don't BUG() on exotic hardware On x86, iommu_get_ops() BUG()s when running on non-Intel, non-AMD hardware. While, with our current code, that's a correct prerequisite assumption for IOMMU presence, this is wrong on systems without IOMMU. Hence iommu_enabled (and alike) checks should be done prior to calling that function, not after. Also move iommu_suspend() next to iommu_resume() - it escapes me why iommu_do_domctl() had got put between the two. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Release-acked-by: Wei Liu <wei.liu2@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 |