|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [xen-unstable test] 13302: regressions - FAIL
On Fri, 2012-06-22 at 04:00 +0100, xen.org wrote: > flight 13302 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/13302/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > build-i386-pvops 4 kernel-build fail REGR. vs. > 13025 > build-i386-oldkern 4 xen-build fail REGR. vs. > 13025 > build-i386 4 xen-build fail REGR. vs. > 13025 These all appear to be timeouts -- some sort of infrastructure problem? > test-amd64-amd64-xl-win7-amd64 7 windows-install fail REGR. vs. > 13025 > test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail REGR. vs. > 13025 > test-amd64-amd64-xl-win 7 windows-install fail REGR. vs. > 13025 > test-amd64-amd64-xl-qemuu-win7-amd64 7 windows-install fail REGR. vs. > 13025 > test-amd64-amd64-xl-winxpsp3 7 windows-install fail REGR. vs. > 13025 These are also timeouts but of the guest initial boot/install. Could be related to the infrastructure issues? I only looked closely at one case (test-amd64-amd64-xl-qemuu-win7-amd64) since they all looked pretty similar. The domain wasn't running when the logs were collect (xl list etc) and the qemu log contains: Issued domain 1 reboot qemu: terminating on signal 1 from pid 3171 so it seems like the installer rebooted the vm but it's not clear if that was after a successful or failed install. The xl log is: Waiting for domain win.guest.osstest (domid 1) to die [pid 3171] Domain 1 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 1 needs to be cleaned up: destroying the domain Which makes me wonder if perhaps HVM virtualised reboot is knackered? This seems plausible given that all the failures were xl related (xend seems ok). I'll investigate this morning. We should hold off on libxl/xl and perhaps HVM related commits until we figure this one out. > Tests which did not succeed, but are not blocking: > test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never > pass > test-amd64-i386-qemuu-rhel6hvm-amd 1 xen-build-check(1) blocked > n/a > test-amd64-i386-rhel6hvm-amd 1 xen-build-check(1) blocked n/a > test-amd64-i386-qemuu-rhel6hvm-intel 1 xen-build-check(1) blocked > n/a > test-amd64-i386-rhel6hvm-intel 1 xen-build-check(1) blocked n/a > test-amd64-i386-pv 1 xen-build-check(1) blocked n/a > test-amd64-i386-xl 1 xen-build-check(1) blocked n/a > test-amd64-i386-xl-credit2 1 xen-build-check(1) blocked n/a > test-amd64-i386-pair 1 xen-build-check(1) blocked n/a > test-amd64-i386-xend-winxpsp3 1 xen-build-check(1) blocked n/a > test-amd64-amd64-win 16 leak-check/check fail never > pass > test-i386-i386-xl 1 xen-build-check(1) blocked n/a > test-amd64-i386-xl-multivcpu 1 xen-build-check(1) blocked n/a > test-i386-i386-pv 1 xen-build-check(1) blocked n/a > test-amd64-i386-win-vcpus1 1 xen-build-check(1) blocked n/a > test-i386-i386-pair 1 xen-build-check(1) blocked n/a > test-amd64-i386-win 1 xen-build-check(1) blocked n/a > test-i386-i386-win 1 xen-build-check(1) blocked n/a > test-amd64-i386-xl-win7-amd64 1 xen-build-check(1) blocked n/a > test-i386-i386-xl-win 1 xen-build-check(1) blocked n/a > test-i386-i386-xl-qemuu-winxpsp3 1 xen-build-check(1) blocked n/a > test-amd64-i386-xl-win-vcpus1 1 xen-build-check(1) blocked n/a > test-i386-i386-xl-winxpsp3 1 xen-build-check(1) blocked n/a > test-amd64-i386-xl-winxpsp3-vcpus1 1 xen-build-check(1) blocked > n/a > > version targeted for testing: > xen 513d5e196e23 > baseline version: > xen 32034d1914a6 > > jobs: > build-amd64 pass > build-i386 fail > build-amd64-oldkern pass > build-i386-oldkern fail > build-amd64-pvops pass > build-i386-pvops fail > test-amd64-amd64-xl pass > test-amd64-i386-xl blocked > test-i386-i386-xl blocked > test-amd64-i386-rhel6hvm-amd blocked > test-amd64-i386-qemuu-rhel6hvm-amd blocked > test-amd64-amd64-xl-qemuu-win7-amd64 fail > test-amd64-amd64-xl-win7-amd64 fail > test-amd64-i386-xl-win7-amd64 blocked > test-amd64-i386-xl-credit2 blocked > test-amd64-amd64-xl-pcipt-intel fail > test-amd64-i386-rhel6hvm-intel blocked > test-amd64-i386-qemuu-rhel6hvm-intel blocked > test-amd64-i386-xl-multivcpu blocked > test-amd64-amd64-pair pass > test-amd64-i386-pair blocked > test-i386-i386-pair blocked > test-amd64-amd64-xl-sedf-pin pass > test-amd64-amd64-pv pass > test-amd64-i386-pv blocked > test-i386-i386-pv blocked > test-amd64-amd64-xl-sedf pass > test-amd64-i386-win-vcpus1 blocked > test-amd64-i386-xl-win-vcpus1 blocked > test-amd64-i386-xl-winxpsp3-vcpus1 blocked > test-amd64-amd64-win fail > test-amd64-i386-win blocked > test-i386-i386-win blocked > test-amd64-amd64-xl-win fail > test-i386-i386-xl-win blocked > test-amd64-amd64-xl-qemuu-winxpsp3 fail > test-i386-i386-xl-qemuu-winxpsp3 blocked > test-amd64-i386-xend-winxpsp3 blocked > test-amd64-amd64-xl-winxpsp3 fail > test-i386-i386-xl-winxpsp3 blocked > > > ------------------------------------------------------------ > 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. > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@xxxxxxxxxxxxx > http://lists.xen.org/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |