* [qemu-mainline test] 62028: regressions - FAIL
@ 2015-09-17 13:44 osstest service owner
2015-09-17 15:15 ` Ian Campbell
0 siblings, 1 reply; 5+ messages in thread
From: osstest service owner @ 2015-09-17 13:44 UTC (permalink / raw)
To: xen-devel, osstest-admin
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 14411 bytes --]
flight 62028 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/62028/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-amd 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl-pvh-intel 6 xen-boot fail REGR. vs. 61666
test-armhf-armhf-xl-vhd 6 xen-boot fail REGR. vs. 61666
test-armhf-armhf-xl-raw 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl-xsm 6 xen-boot fail REGR. vs. 61666
test-armhf-armhf-xl-arndale 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-xl 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-xl-xsm 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-pair 10 xen-boot/dst_host fail REGR. vs. 61666
test-amd64-amd64-pair 9 xen-boot/src_host fail REGR. vs. 61666
test-amd64-amd64-i386-pvgrub 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl-multivcpu 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-pair 10 xen-boot/dst_host fail REGR. vs. 61666
test-amd64-i386-pair 9 xen-boot/src_host fail REGR. vs. 61666
test-armhf-armhf-xl-multivcpu 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-pygrub 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl-credit2 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-qemuu-rhel6hvm-intel 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-amd64-pvgrub 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl-qcow2 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl-qemuu-ovmf-amd64 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-xl-qcow2 6 xen-boot fail REGR. vs. 61666
test-armhf-armhf-xl-credit2 6 xen-boot fail REGR. vs. 61666
test-armhf-armhf-xl-cubietruck 6 xen-boot fail REGR. vs. 61666
test-armhf-armhf-xl 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-qemuu-rhel6hvm-amd 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-xl-raw 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-freebsd10-amd64 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl-raw 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 6 xen-boot fail REGR. vs. 61666
test-armhf-armhf-xl-xsm 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl-qemuu-debianhvm-amd64 6 xen-boot fail REGR. vs. 61666
test-armhf-armhf-xl-qcow2 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-xl-qemuu-win7-amd64 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-freebsd10-i386 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl-qemuu-win7-amd64 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl-vhd 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-xl-vhd 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-xl-qemuu-debianhvm-amd64 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-xl-qemuu-ovmf-amd64 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-xl-qemuu-winxpsp3 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl-qemuu-winxpsp3 6 xen-boot fail REGR. vs. 61666
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt-raw 6 xen-boot fail REGR. vs. 61666
test-armhf-armhf-libvirt 6 xen-boot fail REGR. vs. 61666
test-armhf-armhf-libvirt-xsm 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-libvirt-pair 10 xen-boot/dst_host fail REGR. vs. 61666
test-amd64-i386-libvirt-pair 9 xen-boot/src_host fail REGR. vs. 61666
test-amd64-amd64-libvirt-pair 10 xen-boot/dst_host fail REGR. vs. 61666
test-amd64-amd64-libvirt-pair 9 xen-boot/src_host fail REGR. vs. 61666
test-amd64-i386-libvirt 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-libvirt-xsm 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-libvirt-xsm 6 xen-boot fail REGR. vs. 61666
test-armhf-armhf-xl-rtds 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-libvirt-qcow2 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-libvirt-raw 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-libvirt 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-libvirt-raw 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-libvirt-qcow2 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-xl-rtds 6 xen-boot fail REGR. vs. 61666
test-amd64-i386-libvirt-vhd 6 xen-boot fail REGR. vs. 61666
test-amd64-amd64-libvirt-vhd 6 xen-boot fail REGR. vs. 61666
test-armhf-armhf-libvirt-qcow2 6 xen-boot fail blocked in 61666
test-armhf-armhf-libvirt-vhd 6 xen-boot fail like 61666
version targeted for testing:
qemuu 2752e5bedb26fa0c7291f810f9f534b688b2f1d2
baseline version:
qemuu fc04a730b7e60f4a62d6260d4eb9c537d1d3643f
Last test of basis 61666 2015-09-09 03:07:40 Z 8 days
Failing since 61767 2015-09-10 17:49:38 Z 6 days 3 attempts
Testing same since 62028 2015-09-15 08:02:37 Z 2 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Alexandre Derumier <aderumier@odiso.com>
Alistair Francis <alistair.francis@xilinx.com>
Andrey Korolyov <andrey@xdel.ru>
Andrey Smetanin <asmetanin@virtuozzo.com>
Aníbal Limón <anibal.limon@linux.intel.com>
Aurelien Jarno <aurelien@aurel32.net>
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Carlos L. Torres <carlos.torres@rackspace.com>
Cornelia Huck <cornelia.huck@de.ibm.com>
Daniel P. Berrange <berrange@redhat.com>
Denis V. Lunev <den@openvz.org>
Don Slutz <dslutz@verizon.com>
Dr. David Alan Gilbert <dgilbert@redhat.com>
Edgar E. Iglesias <edgar.iglesias@xilinx.com>
Eduardo Habkost <ehabkost@redhat.com>
Emilio G. Cota <cota@braap.org>
Fam Zheng <famz@redhat.com>
Gerd Hoffmann <kraxel@redhat.com>
Gonglei <arei.gonglei@huawei.com>
Guenter Roeck <linux@roeck-us.net>
Igor Mammedov <imammedo@redhat.com>
Jan Beulich <jbeulich@suse.com>
Jean-Christophe Dubois <jcd@tribudubois.net>
John Snow <jsnow@redhat.com>
KONRAD Frederic <fred.konrad@greensocs.com>
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Kővágó, Zoltán <DirtY.iCE.hu@gmail.com>
Laszlo Ersek <lersek@redhat.com>
Laurent Desnogues <laurent.desnogues@gmail.com>
Laurent Vivier <lvivier@redhat.com>
Marc-André Lureau <marcandre.lureau@redhat.com>
Markus Armbruster <armbru@redhat.com>
Michael Marineau <michael.marineau@coreos.com>
Michael S. Tsirkin <mst@redhat.com>
Michael Tokarev <mjt@tls.msk.ru>
Nathan Rossi <nathan@nathanrossi.com>
Paolo Bonzini <pbonzini@redhat.com>
Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>
Peter Crosthwaite <crosthwaite.peter@gmail.com>
Peter Crosthwaite <crosthwaitepeter@gmail.com>
Peter Lieven <pl@kamp.de>
Peter Maydell <peter.maydell@linaro.org>
Richard Henderson <rth@twiddle.net>
Richard W.M. Jones <rjones@redhat.com>
Samuel Thibault <samuel.thibault@ens-lyon.org>
Samuel Thibault <samuel.thibault@gnu.org>
Shannon Zhao <shannon.zhao@linaro.org>
Shannon Zhao <zhaoshenglong@huawei.com>
Shraddha Barke <shraddha.6596@gmail.com>
Stefan Weil <sw@weilnetz.de>
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Tiejun Chen <tiejun.chen@intel.com>
Veres Lajos <vlajos@gmail.com>
Yang Zhang <yang.z.zhang@Intel.com>
jobs:
build-amd64-xsm pass
build-armhf-xsm pass
build-i386-xsm pass
build-amd64 pass
build-armhf pass
build-i386 pass
build-amd64-libvirt pass
build-armhf-libvirt pass
build-i386-libvirt pass
build-amd64-pvops pass
build-armhf-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl fail
test-armhf-armhf-xl fail
test-amd64-i386-xl fail
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm fail
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm fail
test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm fail
test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm fail
test-amd64-amd64-libvirt-xsm fail
test-armhf-armhf-libvirt-xsm fail
test-amd64-i386-libvirt-xsm fail
test-amd64-amd64-xl-xsm fail
test-armhf-armhf-xl-xsm fail
test-amd64-i386-xl-xsm fail
test-amd64-amd64-xl-pvh-amd fail
test-amd64-i386-qemuu-rhel6hvm-amd fail
test-amd64-amd64-xl-qemuu-debianhvm-amd64 fail
test-amd64-i386-xl-qemuu-debianhvm-amd64 fail
test-amd64-i386-freebsd10-amd64 fail
test-amd64-amd64-xl-qemuu-ovmf-amd64 fail
test-amd64-i386-xl-qemuu-ovmf-amd64 fail
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 fail
test-armhf-armhf-xl-arndale fail
test-amd64-amd64-xl-credit2 fail
test-armhf-armhf-xl-credit2 fail
test-armhf-armhf-xl-cubietruck fail
test-amd64-i386-freebsd10-i386 fail
test-amd64-amd64-xl-pvh-intel fail
test-amd64-i386-qemuu-rhel6hvm-intel fail
test-amd64-amd64-libvirt fail
test-armhf-armhf-libvirt fail
test-amd64-i386-libvirt fail
test-amd64-amd64-xl-multivcpu fail
test-armhf-armhf-xl-multivcpu fail
test-amd64-amd64-pair fail
test-amd64-i386-pair fail
test-amd64-amd64-libvirt-pair fail
test-amd64-i386-libvirt-pair fail
test-amd64-amd64-amd64-pvgrub fail
test-amd64-amd64-i386-pvgrub fail
test-amd64-amd64-pygrub fail
test-amd64-amd64-libvirt-qcow2 fail
test-armhf-armhf-libvirt-qcow2 fail
test-amd64-i386-libvirt-qcow2 fail
test-amd64-amd64-xl-qcow2 fail
test-armhf-armhf-xl-qcow2 fail
test-amd64-i386-xl-qcow2 fail
test-amd64-amd64-libvirt-raw fail
test-armhf-armhf-libvirt-raw fail
test-amd64-i386-libvirt-raw fail
test-amd64-amd64-xl-raw fail
test-armhf-armhf-xl-raw fail
test-amd64-i386-xl-raw fail
test-amd64-amd64-xl-rtds fail
test-armhf-armhf-xl-rtds fail
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail
test-amd64-amd64-libvirt-vhd fail
test-armhf-armhf-libvirt-vhd fail
test-amd64-i386-libvirt-vhd fail
test-amd64-amd64-xl-vhd fail
test-armhf-armhf-xl-vhd fail
test-amd64-i386-xl-vhd fail
test-amd64-amd64-xl-qemuu-winxpsp3 fail
test-amd64-i386-xl-qemuu-winxpsp3 fail
------------------------------------------------------------
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.
(No revision log; it would be 2714 lines long.)
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [qemu-mainline test] 62028: regressions - FAIL
2015-09-17 13:44 [qemu-mainline test] 62028: regressions - FAIL osstest service owner
@ 2015-09-17 15:15 ` Ian Campbell
2015-09-17 18:04 ` Anthony PERARD
0 siblings, 1 reply; 5+ messages in thread
From: Ian Campbell @ 2015-09-17 15:15 UTC (permalink / raw)
To: osstest service owner, xen-devel, Anthony PERARD, Stefano Stabellini
Stefano, Anthony,
This looks like a real upstream regression.
On Thu, 2015-09-17 at 13:44 +0000, osstest service owner wrote:
> flight 62028 qemu-mainline real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/62028/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-pvh-amd 6 xen-boot fail REGR. vs. 61666
> test-amd64-amd64-xl-pvh-intel 6 xen-boot fail REGR. vs. 61666
> test-armhf-armhf-xl-vhd 6 xen-boot fail REGR. vs. 61666
[...many more for every test-*...]
I looked at test-*-*-xl and they all seem to have hung at "Starting QEMU as
disk backend for dom0".
In this flight http://logs.test-lab.xenproject.org/osstest/logs/62028/test-
amd64-amd64-xl/serial-chardonnay1.log ends with:
Sep 17 11:58:48.589051 Starting QEMU as disk backend for dom0
Sep 17 11:58:48.589081
Sep 17 11:59:41.890612 <client 0x93c470 connected - now 1 clients>
(the new client is going to hit the debug keys after the timeout)
By comparison 61666 has in http://logs.test-lab.xenproject.org/osstest/logs
/61666/test-amd64-amd64-xl/serial-elbling0.log
Sep 10 13:31:52.273142 Starting QEMU as disk backend for dom0
Sep 10 13:31:52.273183 Starting NTP server: ntpd.
Sep 10 13:32:18.613286 ^[[r^[[H^[[J
Sep 10 13:32:18.652996 Debian GNU/Linux 7 elbling0 hvc0
i.e. normally dom0's qemu starts almost instantly.
Given the number of failures here this seems unlikely to be host specific
and almost certain represents a bug in qemu-mainline.
It was noted on xen-users this morning that there is no logging from this
qemu instance -- fixing that would be well worthwhile I think.
http://logs.test-lab.xenproject.org/osstest/logs/62028/test-amd64-amd64-xl/chardonnay1-output-ps_wwwaxf_-eo_pid%2Ctty%2Cstat%2Ctime%2Cnice%2Cpsr%2Cpcpu%2Cpmem%2Cnwchan%2Cwchan%2325%2Cargs
shows the process:
3638 ? SL 00:00:00 0 3 0.3 0.5 1d1054 poll_schedule_timeout \_ startpar -p 4 -t 20 -T 3 -M start -P N -R 2
3815 ? S 00:00:00 0 0 0.0 0.3 b0482 wait \_ /bin/bash /etc/init.d/xencommons start
4053 ? Sl 00:00:00 0 1 0.0 1.6 ffffff pipe_wait \_ /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 0 -xen-attach -name dom0 -nographic -M xenpv -daemonize -monitor /dev/null -serial /dev/null -parallel /dev/null -pidfile /var/run/qemu-dom0.pid
4171 ? Ss 00:00:00 0 2 0.0 0.5 113cd9 futex_wait_queue_me \_ /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 0 -xen-attach -name dom0 -nographic -M xenpv -daemonize -monitor /dev/null -serial /dev/null -parallel /dev/null -pidfile /var/run/qemu-dom0.pid
The bisector seems to have started working on this in
http://logs.test-lab.xenproject.org/osstest/results/bisect/qemu-mainline/te
st-amd64-amd64-xl-pvh-amd.xen-boot.html
Ian.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [qemu-mainline test] 62028: regressions - FAIL
2015-09-17 15:15 ` Ian Campbell
@ 2015-09-17 18:04 ` Anthony PERARD
2015-09-17 18:36 ` Anthony PERARD
0 siblings, 1 reply; 5+ messages in thread
From: Anthony PERARD @ 2015-09-17 18:04 UTC (permalink / raw)
To: Ian Campbell; +Cc: xen-devel, osstest service owner, Stefano Stabellini
On Thu, Sep 17, 2015 at 04:15:37PM +0100, Ian Campbell wrote:
> On Thu, 2015-09-17 at 13:44 +0000, osstest service owner wrote:
> > flight 62028 qemu-mainline real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/62028/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > test-amd64-amd64-xl-pvh-amd 6 xen-boot fail REGR. vs. 61666
> > test-amd64-amd64-xl-pvh-intel 6 xen-boot fail REGR. vs. 61666
> > test-armhf-armhf-xl-vhd 6 xen-boot fail REGR. vs. 61666
> [...many more for every test-*...]
>
> I looked at test-*-*-xl and they all seem to have hung at "Starting QEMU as
> disk backend for dom0".
>
> In this flight http://logs.test-lab.xenproject.org/osstest/logs/62028/test-
> amd64-amd64-xl/serial-chardonnay1.log ends with:
>
> Sep 17 11:58:48.589051 Starting QEMU as disk backend for dom0
> Sep 17 11:58:48.589081
> Sep 17 11:59:41.890612 <client 0x93c470 connected - now 1 clients>
> (the new client is going to hit the debug keys after the timeout)
>
> By comparison 61666 has in http://logs.test-lab.xenproject.org/osstest/logs
> /61666/test-amd64-amd64-xl/serial-elbling0.log
>
> Sep 10 13:31:52.273142 Starting QEMU as disk backend for dom0
> Sep 10 13:31:52.273183 Starting NTP server: ntpd.
> Sep 10 13:32:18.613286 ^[[r^[[H^[[J
>
> Sep 10 13:32:18.652996 Debian GNU/Linux 7 elbling0 hvc0
>
> i.e. normally dom0's qemu starts almost instantly.
>
> Given the number of failures here this seems unlikely to be host specific
> and almost certain represents a bug in qemu-mainline.
>
> It was noted on xen-users this morning that there is no logging from this
> qemu instance -- fixing that would be well worthwhile I think.
I don't think there is anything to do on systems using systemd, we can find
the stdout and stderr in the system logs. What does debian with the stdout
and stderr of a service?
> http://logs.test-lab.xenproject.org/osstest/logs/62028/test-amd64-amd64-xl/chardonnay1-output-ps_wwwaxf_-eo_pid%2Ctty%2Cstat%2Ctime%2Cnice%2Cpsr%2Cpcpu%2Cpmem%2Cnwchan%2Cwchan%2325%2Cargs
>
> shows the process:
>
> 3638 ? SL 00:00:00 0 3 0.3 0.5 1d1054 poll_schedule_timeout \_ startpar -p 4 -t 20 -T 3 -M start -P N -R 2
> 3815 ? S 00:00:00 0 0 0.0 0.3 b0482 wait \_ /bin/bash /etc/init.d/xencommons start
> 4053 ? Sl 00:00:00 0 1 0.0 1.6 ffffff pipe_wait \_ /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 0 -xen-attach -name dom0 -nographic -M xenpv -daemonize -monitor /dev/null -serial /dev/null -parallel /dev/null -pidfile /var/run/qemu-dom0.pid
> 4171 ? Ss 00:00:00 0 2 0.0 0.5 113cd9 futex_wait_queue_me \_ /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 0 -xen-attach -name dom0 -nographic -M xenpv -daemonize -monitor /dev/null -serial /dev/null -parallel /dev/null -pidfile /var/run/qemu-dom0.pid
>
> The bisector seems to have started working on this in
http://logs.test-lab.xenproject.org/osstest/results/bisect/qemu-mainline/test-amd64-amd64-xl-pvh-amd.xen-boot.html
I found the first commit that have the same behavior:
commit 5243722376873a48e9852a58b91f4d4101ee66e4
rcu: init rcu_registry_lock after fork
--
Anthony PERARD
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [qemu-mainline test] 62028: regressions - FAIL
2015-09-17 18:04 ` Anthony PERARD
@ 2015-09-17 18:36 ` Anthony PERARD
2015-09-18 8:39 ` Ian Campbell
0 siblings, 1 reply; 5+ messages in thread
From: Anthony PERARD @ 2015-09-17 18:36 UTC (permalink / raw)
To: Ian Campbell; +Cc: xen-devel, osstest service owner, Stefano Stabellini
On Thu, Sep 17, 2015 at 07:04:50PM +0100, Anthony PERARD wrote:
> On Thu, Sep 17, 2015 at 04:15:37PM +0100, Ian Campbell wrote:
> > On Thu, 2015-09-17 at 13:44 +0000, osstest service owner wrote:
> > > flight 62028 qemu-mainline real [real]
> > > http://logs.test-lab.xenproject.org/osstest/logs/62028/
> > >
> > > Regressions :-(
> > >
> > > Tests which did not succeed and are blocking,
> > > including tests which could not be run:
> > > test-amd64-amd64-xl-pvh-amd 6 xen-boot fail REGR. vs. 61666
> > > test-amd64-amd64-xl-pvh-intel 6 xen-boot fail REGR. vs. 61666
> > > test-armhf-armhf-xl-vhd 6 xen-boot fail REGR. vs. 61666
> > [...many more for every test-*...]
> >
> > I looked at test-*-*-xl and they all seem to have hung at "Starting QEMU as
> > disk backend for dom0".
> >
> > In this flight http://logs.test-lab.xenproject.org/osstest/logs/62028/test-
> > amd64-amd64-xl/serial-chardonnay1.log ends with:
> >
> > Sep 17 11:58:48.589051 Starting QEMU as disk backend for dom0
> > Sep 17 11:58:48.589081
> > Sep 17 11:59:41.890612 <client 0x93c470 connected - now 1 clients>
> > (the new client is going to hit the debug keys after the timeout)
> >
> > By comparison 61666 has in http://logs.test-lab.xenproject.org/osstest/logs
> > /61666/test-amd64-amd64-xl/serial-elbling0.log
> >
> > Sep 10 13:31:52.273142 Starting QEMU as disk backend for dom0
> > Sep 10 13:31:52.273183 Starting NTP server: ntpd.
> > Sep 10 13:32:18.613286 ^[[r^[[H^[[J
> >
> > Sep 10 13:32:18.652996 Debian GNU/Linux 7 elbling0 hvc0
> >
> > i.e. normally dom0's qemu starts almost instantly.
> >
> > Given the number of failures here this seems unlikely to be host specific
> > and almost certain represents a bug in qemu-mainline.
> >
> > http://logs.test-lab.xenproject.org/osstest/logs/62028/test-amd64-amd64-xl/chardonnay1-output-ps_wwwaxf_-eo_pid%2Ctty%2Cstat%2Ctime%2Cnice%2Cpsr%2Cpcpu%2Cpmem%2Cnwchan%2Cwchan%2325%2Cargs
> >
> > shows the process:
> >
> > 3638 ? SL 00:00:00 0 3 0.3 0.5 1d1054 poll_schedule_timeout \_ startpar -p 4 -t 20 -T 3 -M start -P N -R 2
> > 3815 ? S 00:00:00 0 0 0.0 0.3 b0482 wait \_ /bin/bash /etc/init.d/xencommons start
> > 4053 ? Sl 00:00:00 0 1 0.0 1.6 ffffff pipe_wait \_ /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 0 -xen-attach -name dom0 -nographic -M xenpv -daemonize -monitor /dev/null -serial /dev/null -parallel /dev/null -pidfile /var/run/qemu-dom0.pid
> > 4171 ? Ss 00:00:00 0 2 0.0 0.5 113cd9 futex_wait_queue_me \_ /usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 0 -xen-attach -name dom0 -nographic -M xenpv -daemonize -monitor /dev/null -serial /dev/null -parallel /dev/null -pidfile /var/run/qemu-dom0.pid
> >
> > The bisector seems to have started working on this in
> http://logs.test-lab.xenproject.org/osstest/results/bisect/qemu-mainline/test-amd64-amd64-xl-pvh-amd.xen-boot.html
>
> I found the first commit that have the same behavior:
> commit 5243722376873a48e9852a58b91f4d4101ee66e4
> rcu: init rcu_registry_lock after fork
The commit have been reverted, so everything should be back to normal.
--
Anthony PERARD
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [qemu-mainline test] 62028: regressions - FAIL
2015-09-17 18:36 ` Anthony PERARD
@ 2015-09-18 8:39 ` Ian Campbell
0 siblings, 0 replies; 5+ messages in thread
From: Ian Campbell @ 2015-09-18 8:39 UTC (permalink / raw)
To: Anthony PERARD; +Cc: xen-devel, osstest service owner, Stefano Stabellini
On Thu, 2015-09-17 at 19:36 +0100, Anthony PERARD wrote:
> The commit have been reverted, so everything should be back to normal.
Great, thanks.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-09-18 8:39 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-09-17 13:44 [qemu-mainline test] 62028: regressions - FAIL osstest service owner
2015-09-17 15:15 ` Ian Campbell
2015-09-17 18:04 ` Anthony PERARD
2015-09-17 18:36 ` Anthony PERARD
2015-09-18 8:39 ` Ian Campbell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).