xen.org
2012-Apr-09 18:18 UTC
[linux-linus test] 12620: regressions - trouble: blocked/broken/fail/pass
flight 12620 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12620/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-pvops 2 host-install(2) broken REGR. vs. 12557 build-i386 2 host-install(2) broken REGR. vs. 12557 test-amd64-amd64-xl-win 3 host-install(3) broken REGR. vs. 12557 test-amd64-i386-xl 7 debian-install fail in 12609 REGR. vs. 12557 test-amd64-i386-xend-winxpsp3 3 host-install(3) broken in 12609 REGR. vs. 12557 Tests which are failing intermittently (not blocking): test-amd64-amd64-xl-sedf-pin 14 guest-localmigrate/x10 fail pass in 12609 test-amd64-amd64-xl 3 host-install(3) broken pass in 12609 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-sedf 9 guest-start fail REGR. vs. 12557 Tests which did not succeed, but are not blocking: 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-win7-amd64 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-win-vcpus1 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-qemuu-rhel6hvm-intel 1 xen-build-check(1) blocked n/a test-amd64-amd64-xl-qemuu-win7-amd64 5 xen-boot fail never pass test-amd64-i386-win 1 xen-build-check(1) blocked n/a test-amd64-i386-rhel6hvm-amd 1 xen-build-check(1) blocked n/a test-amd64-i386-win-vcpus1 1 xen-build-check(1) blocked n/a test-amd64-i386-xl 1 xen-build-check(1) blocked n/a test-amd64-i386-qemuu-rhel6hvm-amd 1 xen-build-check(1) blocked n/a test-i386-i386-pv 1 xen-build-check(1) blocked n/a test-amd64-i386-xl-multivcpu 1 xen-build-check(1) blocked n/a test-amd64-i386-pair 1 xen-build-check(1) blocked n/a test-i386-i386-pair 1 xen-build-check(1) blocked n/a test-amd64-amd64-xl-pcipt-intel 5 xen-boot fail never pass test-amd64-i386-xend-winxpsp3 1 xen-build-check(1) blocked n/a test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never pass test-i386-i386-xl 1 xen-build-check(1) blocked n/a test-amd64-i386-xl-winxpsp3-vcpus1 1 xen-build-check(1) blocked n/a test-amd64-i386-xl-credit2 1 xen-build-check(1) blocked n/a test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail never pass test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass test-i386-i386-win 1 xen-build-check(1) blocked n/a test-i386-i386-xl-win 1 xen-build-check(1) blocked n/a test-amd64-amd64-win 16 leak-check/check fail never pass test-amd64-i386-rhel6hvm-intel 5 xen-boot fail in 12609 never pass test-amd64-i386-pv 5 xen-boot fail in 12609 never pass test-amd64-i386-xl-win7-amd64 5 xen-boot fail in 12609 never pass test-i386-i386-xl-winxpsp3 5 xen-boot fail in 12609 never pass test-amd64-i386-xl-win-vcpus1 5 xen-boot fail in 12609 never pass test-i386-i386-xl-qemuu-winxpsp3 5 xen-boot fail in 12609 never pass test-amd64-i386-qemuu-rhel6hvm-intel 5 xen-boot fail in 12609 never pass test-amd64-i386-win 5 xen-boot fail in 12609 never pass test-amd64-i386-win-vcpus1 5 xen-boot fail in 12609 never pass test-amd64-i386-qemuu-rhel6hvm-amd 7 redhat-install fail in 12609 never pass test-amd64-i386-xl-multivcpu 7 debian-install fail in 12609 never pass test-i386-i386-pair 11 debian-install/dst_host fail in 12609 never pass test-i386-i386-xl 7 debian-install fail in 12609 never pass test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail in 12609 never pass test-i386-i386-win 16 leak-check/check fail in 12609 never pass test-i386-i386-xl-win 13 guest-stop fail in 12609 never pass version targeted for testing: linux 0034102808e0dbbf3a2394b82b1bb40b5778de9e baseline version: linux c16fa4f2ad19908a47c63d8fa436a1178438c7e7 jobs: build-amd64 pass build-i386 broken build-amd64-pvops pass build-i386-pvops broken test-amd64-amd64-xl broken 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 fail test-amd64-amd64-pv pass test-amd64-i386-pv blocked test-i386-i386-pv blocked test-amd64-amd64-xl-sedf fail 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 broken 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.
Konrad Rzeszutek Wilk
2012-Apr-09 22:32 UTC
Re: [linux-linus test] 12620: regressions - trouble: blocked/broken/fail/pass
On Mon, Apr 09, 2012 at 07:18:24PM +0100, xen.org wrote:> flight 12620 linux-linus real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/12620/ > version targeted for testing:.. snip..> linux 0034102808e0dbbf3a2394b82b1bb40b5778de9eHm, that version should have worked.> baseline version: > linux c16fa4f2ad19908a47c63d8fa436a1178438c7e7 > > jobs: > build-amd64 pass > build-i386 brokenAh, so b/c of that the other things broke. I am not actually sure what is broken except that the initrd looks to have not been pushed properly?
Ian Jackson
2012-Apr-10 10:49 UTC
Re: [linux-linus test] 12620: regressions - trouble: blocked/broken/fail/pass [and 1 more messages]
Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [linux-linus test] 12620: regressions - trouble: blocked/broken/fail/pass"):> On Mon, Apr 09, 2012 at 07:18:24PM +0100, xen.org wrote: > > flight 12620 linux-linus real [real] > > http://www.chiark.greenend.org.uk/~xensrcts/logs/12620/ > > version targeted for testing: > .. snip.. > > linux 0034102808e0dbbf3a2394b82b1bb40b5778de9e > > Hm, that version should have worked.Thanks for looking.> > jobs: > > build-amd64 pass > > build-i386 broken > > Ah, so b/c of that the other things broke. I am not actually > sure what is broken except that the initrd looks to have not been > pushed properly?These failures:> Tests which did not succeed and are blocking, > including tests which could not be run: > build-i386-pvops 2 host-install(2) broken REGR. vs. 12557 > build-i386 2 host-install(2) broken REGR. vs. 12557 > test-amd64-amd64-xl-win 3 host-install(3) broken REGR. vs. 12557 > test-amd64-i386-xend-winxpsp3 3 host-install(3) broken in 12609 REGR. vs. 12557are because one my my test boxes forgot how to boot from its network card and reverted to booting from its hard disk. It seems that something I am doing to my machines (perhaps the repeated power cycling) makes this happen occasionally - the machine forgets its boot order. I have "fixed" this machine. (I haven''t bothered trying to get this fixed by the suppliers because it happens to each affected machine only once in several months.)> test-amd64-i386-xl 7 debian-install fail in 12609 REGR. vs. 12557This is a different failure. It appears to be an intermittent problem. At the time only dom0 was running. The step that failed was doing a debootstrap of a Debian guest, which is heavy on disk and network IO. The failure was that it took more than 2000 seconds. This operation does depend on services from the Internet, notably our local debian cacheing proxy and also security.debian.org. It''s most likely that this was a transient problem with security.debian.org although I don''t see any direct evidence for that theory. Ian.