Re: [xen-unstable test] 149520: regressions - FAIL
On 09.04.20 12:35, Jan Beulich wrote: On 09.04.2020 12:23, Jürgen Groß wrote: On 09.04.20 11:00, Jan Beulich wrote: On 09.04.2020 10:56, Jürgen Groß wrote: On 09.04.20 10:00, Jan Beulich wrote: On 09.04.2020 09:31, Jürgen Groß wrote: On 09.04.20 04:30, osstest service owner wrote: flight 149520 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/149520/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-saverestore fail REGR. vs. 149478 test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 149478 Is it possible to get the ioemu-stubdom binary used in those tests? Isn't this the usr/local/lib/xen/boot/ioemu-stubdom.gz in http://logs.test-lab.xenproject.org/osstest/logs/149520/build-amd64-xsm/build/dist.tar.gz No, the crashed one was a 32-bit stubdom, while this file is a 64-bit one. According to the log the path should be fine, but the file in no way matches the crashed one. Then look under http://logs.test-lab.xenproject.org/osstest/logs/149520/build-i386-xsm/build/ or any of the other http://logs.test-lab.xenproject.org/osstest/logs/149520/build-*/build/? I'm pretty sure all produced binaries get collected and made available. Yes, there it could be found. I'm still struggling to understand why the stubdom is built as 32-bit binary for this test. Aiui in test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm the first amd64 stands for the host (Xen) architecture, the last for the guest one, and the i386 for the tool stack's. I assume the stubdom binary chosen is picked based on the tool stack properties, despite it running in a different domain. I have managed to reproduce the problem. It happens only in 32-bit ioemu-stubdom, not in 64-bit. It happens only with the guest's vif configured with "type=ioemu". This makes Mini-OS commit d225f4012d69a19 suspicious, and I think I have found a double free() in it. Will send a patch. Juergen
Re: [xen-unstable test] 149520: regressions - FAIL
On 09.04.2020 12:23, Jürgen Groß wrote: > On 09.04.20 11:00, Jan Beulich wrote: >> On 09.04.2020 10:56, Jürgen Groß wrote: >>> On 09.04.20 10:00, Jan Beulich wrote: On 09.04.2020 09:31, Jürgen Groß wrote: > On 09.04.20 04:30, osstest service owner wrote: >> flight 149520 xen-unstable real [real] >> http://logs.test-lab.xenproject.org/osstest/logs/149520/ >> >> Regressions :-( >> >> Tests which did not succeed and are blocking, >> including tests which could not be run: >> test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 >> guest-saverestore fail REGR. vs. 149478 >> test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 10 >> debian-hvm-install fail REGR. vs. 149478 > > Is it possible to get the ioemu-stubdom binary used in those tests? Isn't this the usr/local/lib/xen/boot/ioemu-stubdom.gz in http://logs.test-lab.xenproject.org/osstest/logs/149520/build-amd64-xsm/build/dist.tar.gz >>> >>> No, the crashed one was a 32-bit stubdom, while this file is a 64-bit >>> one. According to the log the path should be fine, but the file in no >>> way matches the crashed one. >> >> Then look under >> http://logs.test-lab.xenproject.org/osstest/logs/149520/build-i386-xsm/build/ >> or any of the other >> http://logs.test-lab.xenproject.org/osstest/logs/149520/build-*/build/? >> I'm pretty sure all produced binaries get collected and made available. > > Yes, there it could be found. > > I'm still struggling to understand why the stubdom is built as 32-bit > binary for this test. Aiui in test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm the first amd64 stands for the host (Xen) architecture, the last for the guest one, and the i386 for the tool stack's. I assume the stubdom binary chosen is picked based on the tool stack properties, despite it running in a different domain. Jan
Re: [xen-unstable test] 149520: regressions - FAIL
On 09.04.20 11:00, Jan Beulich wrote: On 09.04.2020 10:56, Jürgen Groß wrote: On 09.04.20 10:00, Jan Beulich wrote: On 09.04.2020 09:31, Jürgen Groß wrote: On 09.04.20 04:30, osstest service owner wrote: flight 149520 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/149520/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-saverestore fail REGR. vs. 149478 test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 149478 Is it possible to get the ioemu-stubdom binary used in those tests? Isn't this the usr/local/lib/xen/boot/ioemu-stubdom.gz in http://logs.test-lab.xenproject.org/osstest/logs/149520/build-amd64-xsm/build/dist.tar.gz No, the crashed one was a 32-bit stubdom, while this file is a 64-bit one. According to the log the path should be fine, but the file in no way matches the crashed one. Then look under http://logs.test-lab.xenproject.org/osstest/logs/149520/build-i386-xsm/build/ or any of the other http://logs.test-lab.xenproject.org/osstest/logs/149520/build-*/build/? I'm pretty sure all produced binaries get collected and made available. Yes, there it could be found. I'm still struggling to understand why the stubdom is built as 32-bit binary for this test. Juergen
Re: [xen-unstable test] 149520: regressions - FAIL
On 09.04.2020 10:56, Jürgen Groß wrote: > On 09.04.20 10:00, Jan Beulich wrote: >> On 09.04.2020 09:31, Jürgen Groß wrote: >>> On 09.04.20 04:30, osstest service owner wrote: flight 149520 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/149520/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-saverestore fail REGR. vs. 149478 test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 149478 >>> >>> Is it possible to get the ioemu-stubdom binary used in those tests? >> >> Isn't this the usr/local/lib/xen/boot/ioemu-stubdom.gz in >> http://logs.test-lab.xenproject.org/osstest/logs/149520/build-amd64-xsm/build/dist.tar.gz > > No, the crashed one was a 32-bit stubdom, while this file is a 64-bit > one. According to the log the path should be fine, but the file in no > way matches the crashed one. Then look under http://logs.test-lab.xenproject.org/osstest/logs/149520/build-i386-xsm/build/ or any of the other http://logs.test-lab.xenproject.org/osstest/logs/149520/build-*/build/? I'm pretty sure all produced binaries get collected and made available. Jan
Re: [xen-unstable test] 149520: regressions - FAIL
On 09.04.20 10:00, Jan Beulich wrote: On 09.04.2020 09:31, Jürgen Groß wrote: On 09.04.20 04:30, osstest service owner wrote: flight 149520 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/149520/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-saverestore fail REGR. vs. 149478 test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 149478 Is it possible to get the ioemu-stubdom binary used in those tests? Isn't this the usr/local/lib/xen/boot/ioemu-stubdom.gz in http://logs.test-lab.xenproject.org/osstest/logs/149520/build-amd64-xsm/build/dist.tar.gz No, the crashed one was a 32-bit stubdom, while this file is a 64-bit one. According to the log the path should be fine, but the file in no way matches the crashed one. Juergen
Re: [xen-unstable test] 149520: regressions - FAIL
On 09.04.2020 09:31, Jürgen Groß wrote: > On 09.04.20 04:30, osstest service owner wrote: >> flight 149520 xen-unstable real [real] >> http://logs.test-lab.xenproject.org/osstest/logs/149520/ >> >> Regressions :-( >> >> Tests which did not succeed and are blocking, >> including tests which could not be run: >> test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-saverestore >> fail REGR. vs. 149478 >> test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install >> fail REGR. vs. 149478 > > Is it possible to get the ioemu-stubdom binary used in those tests? Isn't this the usr/local/lib/xen/boot/ioemu-stubdom.gz in http://logs.test-lab.xenproject.org/osstest/logs/149520/build-amd64-xsm/build/dist.tar.gz Jan > I'm seeing a crash in: > > http://logs.test-lab.xenproject.org/osstest/logs/149520/test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm/huxelrebe1---var-log-xen-qemu-dm-debianhvm.guest.osstest.log > > and I'd like to get symbol+offset for the stack backtrace. > > > Juergen >
Re: [xen-unstable test] 149520: regressions - FAIL
On 09.04.20 04:30, osstest service owner wrote: flight 149520 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/149520/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-saverestore fail REGR. vs. 149478 test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 149478 Is it possible to get the ioemu-stubdom binary used in those tests? I'm seeing a crash in: http://logs.test-lab.xenproject.org/osstest/logs/149520/test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm/huxelrebe1---var-log-xen-qemu-dm-debianhvm.guest.osstest.log and I'd like to get symbol+offset for the stack backtrace. Juergen
[xen-unstable test] 149520: regressions - FAIL
flight 149520 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/149520/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-saverestore fail REGR. vs. 149478 test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 149478 Tests which are failing intermittently (not blocking): test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail in 149502 pass in 149520 test-armhf-armhf-xl-vhd 18 leak-check/check fail pass in 149502 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-rtds 18 guest-localmigrate/x10 fail like 149431 test-armhf-armhf-libvirt 14 saverestore-support-checkfail like 149478 test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 149478 test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stopfail like 149478 test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stopfail like 149478 test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 149478 test-armhf-armhf-libvirt-raw 13 saverestore-support-checkfail like 149478 test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stopfail like 149478 test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail like 149478 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stopfail like 149478 test-amd64-amd64-libvirt-xsm 13 migrate-support-checkfail never pass test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass test-amd64-i386-libvirt-xsm 13 migrate-support-checkfail never pass test-amd64-i386-xl-pvshim12 guest-start fail never pass test-amd64-i386-libvirt 13 migrate-support-checkfail never pass test-arm64-arm64-xl-seattle 13 migrate-support-checkfail never pass test-arm64-arm64-xl-seattle 14 saverestore-support-checkfail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2 fail never pass test-arm64-arm64-xl-thunderx 13 migrate-support-checkfail never pass test-arm64-arm64-xl 13 migrate-support-checkfail never pass test-arm64-arm64-xl-credit2 13 migrate-support-checkfail never pass test-arm64-arm64-xl-thunderx 14 saverestore-support-checkfail never pass test-arm64-arm64-xl-credit2 14 saverestore-support-checkfail never pass test-arm64-arm64-xl 14 saverestore-support-checkfail never pass test-arm64-arm64-xl-xsm 13 migrate-support-checkfail never pass test-arm64-arm64-xl-xsm 14 saverestore-support-checkfail never pass test-arm64-arm64-libvirt-xsm 13 migrate-support-checkfail never pass test-arm64-arm64-libvirt-xsm 14 saverestore-support-checkfail never pass test-armhf-armhf-xl-arndale 13 migrate-support-checkfail never pass test-armhf-armhf-xl-arndale 14 saverestore-support-checkfail never pass test-arm64-arm64-xl-credit1 13 migrate-support-checkfail never pass test-arm64-arm64-xl-credit1 14 saverestore-support-checkfail never pass test-amd64-amd64-libvirt-vhd 12 migrate-support-checkfail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 13 migrate-support-checkfail never pass test-armhf-armhf-xl-cubietruck 13 migrate-support-checkfail never pass test-armhf-armhf-xl-credit2 14 saverestore-support-checkfail never pass test-armhf-armhf-xl-cubietruck 14 saverestore-support-checkfail never pass test-armhf-armhf-libvirt 13 migrate-support-checkfail never pass test-armhf-armhf-xl-rtds 13 migrate-support-checkfail never pass test-armhf-armhf-xl-rtds 14 saverestore-support-checkfail never pass test-amd64-i386-xl-qemut-ws16-amd64 17 guest-stop fail never pass test-armhf-armhf-xl-multivcpu 13 migrate-support-checkfail never pass test-armhf-armhf-xl-multivcpu 14 saverestore-support-checkfail never pass test-armhf-armhf-xl-credit1 13 migrate-support-checkfail never pass test-armhf-armhf-xl-credit1 14 saverestore-support-checkfail never pass test-armhf-armhf-xl 13 migrate-support-checkfail never pass test-armhf-armhf-xl 14 saverestore-support-checkfail never pass test-armhf-armhf-libvirt-raw 12 migrate-support-checkfail never pass test-armhf-armhf-xl-vhd 12 migrate-support-checkfail never pass test-armhf-armhf-xl-vhd 13 saverestore-support-checkfail never pass version targeted for testing: xen e013e8514389b739153016349e49f5a78e34ddf0 baseline version: xen
