[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-unstable-smoke test] 109577: regressions - trouble: blocked/broken/fail/pass
flight 109577 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/109577/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf 5 xen-build fail REGR. vs. 109547 Tests which did not succeed, but are not blocking: test-armhf-armhf-xl 1 build-check(1) blocked n/a test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a test-amd64-amd64-libvirt 12 migrate-support-check fail never pass version targeted for testing: xen f745b55f137c9c086552dc7463ba2cefccab8292 baseline version: xen a7d4a5904b62731551e366ff62d84759c8ee68e2 Last test of basis 109547 2017-05-17 18:12:36 Z 0 days Testing same since 109570 2017-05-18 10:02:26 Z 0 days 2 attempts ------------------------------------------------------------ People who touched revisions under test: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Samuel Thibault <samuel.thibault@xxxxxxxxxxxx> Steven Haigh <netwiz@xxxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> jobs: build-amd64 pass build-armhf fail build-amd64-libvirt pass test-armhf-armhf-xl blocked test-arm64-arm64-xl-xsm broken test-amd64-amd64-xl-qemuu-debianhvm-i386 pass 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 Not pushing. ------------------------------------------------------------ commit f745b55f137c9c086552dc7463ba2cefccab8292 Author: Wei Liu <wei.liu2@xxxxxxxxxx> Date: Wed May 17 15:26:08 2017 +0100 build: stubdom and tools should depend on public header target Build can fail if stubdom build is run before tools build because: 1. tools/include build uses relative path and depends on XEN_OS 2. stubdom needs tools/include to be built, at which time XEN_OS is mini-os and corresponding symlinks are created 3. libraries inside tools needs tools/include to be built, at which time XEN_OS is the host os name, but symlinks won't be created because they are already there 4. libraries get the wrong headers and fail to build Since both tools and stubdom build need the public headers, we build tools/include before stubdom and tools. Remove runes in stubdom and tools to avoid building tools/include more than once. Provide a new dist target for tools/include. Hook up the install, clean, dist and distclean targets for tools/include. The new arrangement ensures tools build gets the correct headers because XEN_OS is set to host os when building tools/include. As for stubdom, it explicitly links to the mini-os directory without relying on XEN_OS so it should be fine. Reported-by: Steven Haigh <netwiz@xxxxxxxxx> Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> Tested-by: Steven Haigh <netwiz@xxxxxxxxx> Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Release-acked-by: Julien Grall <julien.grall@xxxxxxx> Acked-by: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx> (qemu changes not included) _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/cgi-bin/mailman/listinfo/osstest-output
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |