From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v1 0/2] Merge IO 2017/11/06
Date: Mon, 6 Nov 2017 17:43:38 +0000 [thread overview]
Message-ID: <20171106174338.GP23361@redhat.com> (raw)
In-Reply-To: <CAFEAcA_jweuOwrNf93o=2uMzXQVUHcJ6cNsQd++sRt_D04j1nA@mail.gmail.com>
On Mon, Nov 06, 2017 at 04:11:56PM +0000, Peter Maydell wrote:
> On 6 November 2017 at 15:33, Daniel P. Berrange <berrange@redhat.com> wrote:
> > The following changes since commit ec7a8bf0b8f7dc7288fe8745464ee8217528cc6c:
> >
> > Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2017-11-06 10:04:16 +0000)
> >
> > are available in the git repository at:
> >
> > git://github.com/berrange/qemu tags/pull-qio-2017-11-06-1
> >
> > for you to fetch changes up to 74c0035408d5b327eac5985d976bca3009e0c5d6:
> >
> > tests: Add test-listen - a stress test for QEMU socket listen (2017-11-06 11:49:15 +0000)
> >
> > ----------------------------------------------------------------
> > Merge qio 2017-11-06 v1
> >
> > ----------------------------------------------------------------
>
> Hi. I'm afraid this fails on various hosts.
Sigh, anything network related in unit tests is soo hard to get right :-(
I was hoping the previous fail you saw with this test was all due to the
file descriptor leak the first patch fixed, but I guess not....
>
> arm 32 bit (in a chroot on a 64 bit box):
> TEST: tests/test-listen... (pid=319)
> /socket/listen-serial/ipv4: OK
> /socket/listen-serial/ipv6:
> ** Failed to assign a port to
> thread 0 (errno = 98)
> ** Failed to assign a port to thread 1 (errno = 98)
> ** Failed to assign a port to thread 2 (errno = 98)
> ** Failed to assign a port to thread 3 (errno = 98)
> ** Failed to assign a port to thread 4 (errno = 98)
> [...repeats all the way up to...]
> ** Failed to assign a port to thread 197 (errno = 98)
> ** Failed to assign a port to thread 198 (errno = 98)
> ** Failed to assign a port to thread 199 (errno = 98)
> **
> ERROR:/home/peter.maydell/qemu/tests/test-listen.c:195:listen_compete_nthr:
> assertion failed (failed_listens == 0): (200 == 0)
Hmm, every single thread failed, which suggests some fundamental config in
this environment that prevents any use of networking at all from tests.
Anything interesting about this build env related to network availability
that would prevent use of even localhost ?
> FAIL
> GTester: last random seed: R02Sbad2a742dbd146e85cb412ce8f8f3750
> (pid=321)
> /socket/listen-serial/generic: OK
> /socket/listen-compete/ipv4: OK
> /socket/listen-compete/ipv6: OK
> /socket/listen-compete/generic: OK
> FAIL: tests/test-listen
>
> Compile failure for the test on FreeBSD:
>
> /root/qemu/tests/test-listen.c:53:19: error: use of undeclared
> identifier 'EAI_ADDRFAMILY'
> if (rc == EAI_ADDRFAMILY ||
> ^
Ok, that's at least an easy one to fix.
>
>
> Test failure on OpenBSD:
>
> TEST: tests/test-listen... (pid=9208)
> /socket/listen-serial/ipv4:
> ** Failed to assign a port to
> thread 124 (errno = 48)
> ** Failed to assign a port to thread 125 (errno = 48)
> ** Failed to assign a port to thread 126 (errno = 48)
> ** Failed to assign a port to thread 127 (errno = 48)
> [repeats up to]
> ** Failed to assign a port to thread 197 (errno = 48)
> ** Failed to assign a port to thread 198 (errno = 48)
> ** Failed to assign a port to thread 199 (errno = 48)
> **
> ERROR:/home/qemu/tests/test-listen.c:195:listen_compete_nthr:
> assertion failed (failed_listens == 0): (76 == 0)
> FAIL
> GTester: last random seed: R02S17d50ab00329e514ffbe630191e76e83
> (pid=80652)
Only a subset failed, which is more interesting - this is definitely
more like the problem seen when FD leaks. Could you mention what the
ulimits are for your OpenBSD host - I wondering if it hits max FDs
due to having a parallel builds / test run.
> & similarly for the other subtests.
>
> Linux x86-64:
>
> make: Entering directory '/home/petmay01/linaro/qemu-for-merges/build/all'
> GTESTER tests/test-listen
> ** Failed to assign a port to thread 0 (errno = 98)
> ** Failed to assign a port to thread 1 (errno = 98)
> ** Failed to assign a port to thread 2 (errno = 98)
> ** Failed to assign a port to thread 3 (errno = 98)
> ** Failed to assign a port to thread 4 (errno = 98)
> ** Failed to assign a port to thread 5 (errno = 98)
> ** Failed to assign a port to thread 6 (errno = 98)
> [up to]
> ** Failed to assign a port to thread 199 (errno = 98)
> **
> ERROR:/home/petmay01/linaro/qemu-for-merges/tests/test-listen.c:195:listen_compete_nthr:
> assertion failed (failed_listens == 0): (200 == 0)
> GTester: last random seed: R02S041a056d256c9ae190cf026f5adfd979
> /home/petmay01/linaro/qemu-for-merges/tests/Makefile.include:863:
> recipe for target 'check-tests/test-listen' failed
Looks same as your arm env, which suggests no network access at all.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-11-06 17:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 15:33 [Qemu-devel] [PULL v1 0/2] Merge IO 2017/11/06 Daniel P. Berrange
2017-11-06 15:33 ` [Qemu-devel] [PULL v1 1/2] sockets: avoid leak of listen file descriptor Daniel P. Berrange
2017-11-06 15:33 ` [Qemu-devel] [PULL v1 2/2] tests: Add test-listen - a stress test for QEMU socket listen Daniel P. Berrange
2018-05-01 14:00 ` Knut Omang
2018-05-01 14:07 ` Daniel P. Berrangé
2018-05-01 14:21 ` Knut Omang
2018-05-01 14:36 ` Daniel P. Berrangé
2017-11-06 16:11 ` [Qemu-devel] [PULL v1 0/2] Merge IO 2017/11/06 Peter Maydell
2017-11-06 17:43 ` Daniel P. Berrange [this message]
2017-11-06 17:58 ` Peter Maydell
2017-11-07 9:19 ` Daniel P. Berrange
2017-11-07 14:40 ` Daniel P. Berrange
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171106174338.GP23361@redhat.com \
--to=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.