xen.org
2013-Nov-30 03:44 UTC
[xen-unstable test] 22184: regressions - trouble: broken/fail/pass
flight 22184 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/22184/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail REGR. vs. 22106
test-amd64-i386-xl-win7-amd64 9 guest-localmigrate fail REGR. vs. 22106
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-freebsd10-i386 3 host-install(3) broken blocked in 22106
Tests which did not succeed, but are not blocking:
test-amd64-i386-freebsd10-amd64 7 freebsd-install fail never pass
test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass
test-armhf-armhf-xl 5 xen-boot fail never pass
test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass
test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass
test-amd64-i386-xl-qemut-win7-amd64 13 guest-stop fail never pass
test-amd64-amd64-xl-qemut-winxpsp3 13 guest-stop fail never pass
test-amd64-amd64-xl-win7-amd64 13 guest-stop fail never pass
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check fail never pass
test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop fail never pass
test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass
test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass
version targeted for testing:
xen cb08944a482a5e80a3ff1113f0735761cc4c6cb8
baseline version:
xen e439e0b289e3590f84836e4f9bbdfa560c7af6ef
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Anthony PERARD <anthony.perard@citrix.com>
Anup Patel <anup.patel@linaro.org>
Eddie Dong <eddie.dong@intel.com>
Feng Wu <feng.wu@intel.com>
George Dunlap <george.dunlap@eu.citrix.com>
Ian Campbell <ian.campbell@citrix.com>
Ian Jackson <ian.jackson@eu.citrix.com>
Jan Beulich <jbeulich@suse.com>
Jean-Yves Migeon <jym@NetBSD.org>
Julien Grall <julien.grall@linaro.org>
Julien Grall<julien.grall@linaro.org>
Matthew Daley <mattd@bugfuzz.com>
Mukesh Rathor <mukesh.rathor@oracle.com>
Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>
Paul Durrant <paul.durrant@citrix.com>
Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
Roger Pau Monné <roger.pau@citrix.com>
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Tim Deegan <tim@xen.org>
Wei Liu <wei.liu2@citrix.com>
------------------------------------------------------------
jobs:
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-armhf-armhf-xl fail
test-amd64-i386-xl pass
test-amd64-i386-rhel6hvm-amd pass
test-amd64-i386-qemut-rhel6hvm-amd pass
test-amd64-i386-qemuu-rhel6hvm-amd pass
test-amd64-i386-freebsd10-amd64 fail
test-amd64-amd64-xl-qemut-win7-amd64 fail
test-amd64-i386-xl-qemut-win7-amd64 fail
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-amd64-xl-win7-amd64 fail
test-amd64-i386-xl-win7-amd64 fail
test-amd64-i386-xl-credit2 pass
test-amd64-i386-freebsd10-i386 broken
test-amd64-amd64-xl-pcipt-intel fail
test-amd64-i386-rhel6hvm-intel pass
test-amd64-i386-qemut-rhel6hvm-intel pass
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-i386-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-amd64-amd64-xl-sedf-pin pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-amd64-amd64-xl-sedf pass
test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail
test-amd64-i386-xl-winxpsp3-vcpus1 fail
test-amd64-i386-xend-qemut-winxpsp3 fail
test-amd64-amd64-xl-qemut-winxpsp3 fail
test-amd64-amd64-xl-qemuu-winxpsp3 fail
test-amd64-i386-xend-winxpsp3 fail
test-amd64-amd64-xl-winxpsp3 fail
------------------------------------------------------------
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.
(No revision log; it would be 756 lines long.)
--===============0498272137096320532=Content-Type: text/plain;
charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
--===============0498272137096320532==--
Roger Pau Monné
2013-Nov-30 10:56 UTC
Re: [xen-unstable test] 22184: regressions - trouble: broken/fail/pass
On 30/11/13 04:44, xen.org wrote:> flight 22184 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/22184/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail REGR. vs. 22106 > test-amd64-i386-xl-win7-amd64 9 guest-localmigrate fail REGR. vs. 22106 > > Regressions which are regarded as allowable (not blocking): > test-amd64-i386-freebsd10-i386 3 host-install(3) broken blocked in 22106 > > Tests which did not succeed, but are not blocking: > test-amd64-i386-freebsd10-amd64 7 freebsd-install fail never passBy looking at the logs it seems like if the VG name has ''-'' on it they get replaced to ''--'' by the device mapper, so the right path should be: /dev/mapper/lake--frog-freebsd.guest.osstest--disk3 I have a completely untested patch to fix this (I also have to say my perl skills are really limited, so probably there''s a better way to do this): --- diff --git a/ts-freebsd-install b/ts-freebsd-install index 470fb83..8b0c7bc 100755 --- a/ts-freebsd-install +++ b/ts-freebsd-install @@ -66,8 +66,10 @@ sub prep () { # Use amd64 as default arch ? $r{"$gho->{Guest}_arch"} : ''amd64''). ".qcow2.xz"); - - my $rootpartition_dev = "/dev/mapper/$gho->{Vg}-$gho->{Name}--disk3"; + + my $vg_mapper = $gho->{Vg}; + $vg_mapper =~ s/-/--/g; + my $rootpartition_dev = "/dev/mapper/$vg_mapper-$gho->{Name}--disk3"; target_cmd_root($ho, "umount $gho->{Lvdev} ||:");
Ian Campbell
2013-Nov-30 11:20 UTC
Re: [xen-unstable test] 22184: regressions - trouble: broken/fail/pass
On Sat, 2013-11-30 at 11:56 +0100, Roger Pau Monné wrote:> On 30/11/13 04:44, xen.org wrote: > > flight 22184 xen-unstable real [real] > > http://www.chiark.greenend.org.uk/~xensrcts/logs/22184/ > > > > Regressions :-( > > > > Tests which did not succeed and are blocking, > > including tests which could not be run: > > test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail REGR. vs. 22106 > > test-amd64-i386-xl-win7-amd64 9 guest-localmigrate fail REGR. vs. 22106 > > > > Regressions which are regarded as allowable (not blocking): > > test-amd64-i386-freebsd10-i386 3 host-install(3) broken blocked in 22106 > > > > Tests which did not succeed, but are not blocking: > > test-amd64-i386-freebsd10-amd64 7 freebsd-install fail never pass > > By looking at the logs it seems like if the VG name has ''-'' on it they > get replaced to ''--'' by the device mapper, so the right path should be: > > /dev/mapper/lake--frog-freebsd.guest.osstest--disk3 > > I have a completely untested patch to fix this (I also have to say my > perl skills are really limited, so probably there''s a better way to do > this):You can/should probably abstract Osstest::Debian.pm:lvm_lv_name() into a more common location. Ian.
Jan Beulich
2013-Dec-02 09:36 UTC
Re: [xen-unstable test] 22184: regressions - trouble: broken/fail/pass
>>> On 30.11.13 at 04:44, xen.org <ian.jackson@eu.citrix.com> wrote: > flight 22184 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/22184/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail REGR. vs. 22106Still some fallout from the qemu upgrade? Nov 29 13:22:30.209757 [ 1926.179052] qemu-system-i38[3261]: segfault at 7f3b9ae5f000 ip 00007f3b9f3f8c11 sp 00007fffbc358b68 error 6 in libc-2.11.3.so[7f3b9f379000+159000]> test-amd64-i386-xl-win7-amd64 9 guest-localmigrate fail REGR. vs. > 22106Here I''m also suspecting something in qemu going wrong: For a local migrate test, there would seem to be too many guest reboots being invoked (according to the various qemu-dm log files, namely itch-mite---var-log-xen-qemu-dm-win.guest.osstest--incoming.log). But then again - are the tests here using the newer qemu already? QEMU_TAG in ./Config.mk seems to suggest they wouldn''t (yet I thought we got a push on the qemu-upstream tree)... Jan
Ian Campbell
2013-Dec-02 10:14 UTC
Re: [xen-unstable test] 22184: regressions - trouble: broken/fail/pass
On Mon, 2013-12-02 at 09:36 +0000, Jan Beulich wrote:> >>> On 30.11.13 at 04:44, xen.org <ian.jackson@eu.citrix.com> wrote: > > flight 22184 xen-unstable real [real] > > http://www.chiark.greenend.org.uk/~xensrcts/logs/22184/ > > > > Regressions :-( > > > > Tests which did not succeed and are blocking, > > including tests which could not be run: > > test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail REGR. vs. 22106 > > Still some fallout from the qemu upgrade? > > Nov 29 13:22:30.209757 [ 1926.179052] qemu-system-i38[3261]: segfault at 7f3b9ae5f000 ip 00007f3b9f3f8c11 sp 00007fffbc358b68 error 6 in libc-2.11.3.so[7f3b9f379000+159000] > > > test-amd64-i386-xl-win7-amd64 9 guest-localmigrate fail REGR. vs. > > 22106 > > Here I''m also suspecting something in qemu going wrong: For a > local migrate test, there would seem to be too many guest reboots > being invoked (according to the various qemu-dm log files, namely > itch-mite---var-log-xen-qemu-dm-win.guest.osstest--incoming.log). > > But then again - are the tests here using the newer qemu already? > QEMU_TAG in ./Config.mk seems to suggest they wouldn''t (yet I > thought we got a push on the qemu-upstream tree)...http://www.chiark.greenend.org.uk/~xensrcts/logs/22184/build-amd64/info.html shows built_revision_qemuu b97307ecaad98360f41ea36cd9674ef810c4f8cf, which appears to follow the qemu-1.6 merge changeset, so I think we are testing the new version despite what Config.mk says. Which is good argument for updating Config.mk such that users actually get what we have tested! Ian.
Ian Jackson
2013-Dec-02 11:47 UTC
Re: [xen-unstable test] 22184: regressions - trouble: broken/fail/pass
Ian Campbell writes ("Re: [Xen-devel] [xen-unstable test] 22184:
regressions - trouble: broken/fail/pass"):> On Mon, 2013-12-02 at 09:36 +0000, Jan Beulich wrote:
...> > But then again - are the tests here using the newer qemu already?
> > QEMU_TAG in ./Config.mk seems to suggest they wouldn''t (yet I
> > thought we got a push on the qemu-upstream tree)...
>
>
http://www.chiark.greenend.org.uk/~xensrcts/logs/22184/build-amd64/info.html
shows built_revision_qemuu b97307ecaad98360f41ea36cd9674ef810c4f8cf, which
appears to follow the qemu-1.6 merge changeset, so I think we are testing the
new version despite what Config.mk says. Which is good argument for updating
Config.mk such that users actually get what we have tested!
Indeed.
osstest has its own push gate for the "qemu upstream" branch.
And, and in general, osstest overrides Config.mk''s selections of which
components to use. This is so that it controls and knows exactly what
is being tested.
For the xen-unstable tests, it uses the tested qemu upstream (that is,
the push gate output).
I think Config.mk''s upstream qemu should be updated to refer to
master.
Ian.
Roger Pau Monné
2013-Dec-02 15:22 UTC
Re: [xen-unstable test] 22184: regressions - trouble: broken/fail/pass
On 30/11/13 12:20, Ian Campbell wrote:> On Sat, 2013-11-30 at 11:56 +0100, Roger Pau Monné wrote: >> On 30/11/13 04:44, xen.org wrote: >>> flight 22184 xen-unstable real [real] >>> http://www.chiark.greenend.org.uk/~xensrcts/logs/22184/ >>> >>> Regressions :-( >>> >>> Tests which did not succeed and are blocking, >>> including tests which could not be run: >>> test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail REGR. vs. 22106 >>> test-amd64-i386-xl-win7-amd64 9 guest-localmigrate fail REGR. vs. 22106 >>> >>> Regressions which are regarded as allowable (not blocking): >>> test-amd64-i386-freebsd10-i386 3 host-install(3) broken blocked in 22106 >>> >>> Tests which did not succeed, but are not blocking: >>> test-amd64-i386-freebsd10-amd64 7 freebsd-install fail never pass >> >> By looking at the logs it seems like if the VG name has ''-'' on it they >> get replaced to ''--'' by the device mapper, so the right path should be: >> >> /dev/mapper/lake--frog-freebsd.guest.osstest--disk3 >> >> I have a completely untested patch to fix this (I also have to say my >> perl skills are really limited, so probably there''s a better way to do >> this): > > You can/should probably abstract Osstest::Debian.pm:lvm_lv_name() into a > more common location.I''ve moved it to TestSupport: --- diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm index e51a233..6759263 100644 --- a/Osstest/Debian.pm +++ b/Osstest/Debian.pm @@ -111,15 +111,6 @@ sub bl_getmenu_open ($$$) { return $f; } -sub lvm_lv_name($$) { - my ($ho, $lv) = @_; - - my $vg = "$ho->{Name}"; - # Dashes are escaped in the VG name - $vg =~ s/-/--/g; - return "/dev/mapper/$vg-$lv"; -} - sub setupboot_uboot ($$$) { my ($ho,$want_kernver,$xenhopt,$xenkopt) = @_; my $bl= { }; @@ -131,7 +122,7 @@ sub setupboot_uboot ($$$) { my $kern = "vmlinuz-$want_kernver"; my $initrd = "initrd.img-$want_kernver"; - my $root= lvm_lv_name($ho,"root"); + my $root= target_guest_lv_name($ho,"root"); logm("Xen options: $xenhopt"); logm("Linux options: $xenkopt"); @@ -590,7 +581,7 @@ END } if ( $ho->{Flags}{''need-uboot-bootscr''} ) { - my $root=lvm_lv_name($ho,"root"); + my $root=target_guest_lv_name($ho,"root"); preseed_hook_command($ho, ''late_command'', $sfx, <<END); #!/bin/sh diff --git a/Osstest/TestSupport.pm b/Osstest/TestSupport.pm index 233d453..0398416 100644 --- a/Osstest/TestSupport.pm +++ b/Osstest/TestSupport.pm @@ -57,7 +57,7 @@ BEGIN { target_put_guest_image target_editfile_root target_file_exists target_install_packages target_install_packages_norec - target_extract_jobdistpath + target_extract_jobdistpath target_guest_lv_name poll_loop tcpconnect await_tcp contents_make_cpio file_simple_write_contents @@ -607,6 +607,15 @@ sub poll_loop ($$$&) { logm("$what: ok. (${waited}s)"); } +sub target_guest_lv_name($$) { + my ($ho, $lv) = @_; + + my $vg = "$ho->{Name}"; + # Dashes are escaped in the VG name + $vg =~ s/-/--/g; + return "/dev/mapper/$vg-$lv"; +} + #---------- dhcp watching ---------- sub dhcp_watch_setup ($$) { diff --git a/ts-freebsd-install b/ts-freebsd-install index 470fb83..6c6abbe 100755 --- a/ts-freebsd-install +++ b/ts-freebsd-install @@ -67,7 +67,7 @@ sub prep () { ? $r{"$gho->{Guest}_arch"} : ''amd64''). ".qcow2.xz"); - my $rootpartition_dev = "/dev/mapper/$gho->{Vg}-$gho->{Name}--disk3"; + my $rootpartition_dev = target_guest_lv_name($ho, $gho->{Name}) . "--disk3"; target_cmd_root($ho, "umount $gho->{Lvdev} ||:");
Ian Jackson
2013-Dec-02 15:26 UTC
Re: [xen-unstable test] 22184: regressions - trouble: broken/fail/pass
Roger Pau Monné writes ("Re: [Xen-devel] [xen-unstable test] 22184:
regressions - trouble: broken/fail/pass"):> On 30/11/13 12:20, Ian Campbell wrote:
...> > You can/should probably abstract Osstest::Debian.pm:lvm_lv_name() into
a
> > more common location.
>
> I''ve moved it to TestSupport:
LGTM. I will push this into the mill at some appropriate point.
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
(Sorry for not spotting your earlier mistake. I did read that bit of
the code but failed to join the dots.)
Thanks,
Ian.
Seemingly Similar Threads
- [xen-unstable test] 22043: regressions - trouble: blocked/broken/fail/pass
- [xen-4.2-testing test] 16260: regressions - FAIL
- [PATCH RFC V2 0/6] OSSTest: OVMF test job
- [PATCH/RFC OSSTEST] Debian PV netboot guest test
- [PATCH OSSTEST 0/6] Support for serial logs from marilith boxes