From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Stefan Berger" <stefanb@linux.vnet.ibm.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] tpm_emu_test_wait_cond: code should not be reached
Date: Tue, 8 May 2018 14:48:31 +0100 [thread overview]
Message-ID: <20180508134831.GV5967@redhat.com> (raw)
In-Reply-To: <65983efd-e68f-76f5-bfb1-a8d14045df76@amsat.org>
On Tue, May 08, 2018 at 09:41:05AM -0300, Philippe Mathieu-Daudé wrote:
> Hi,
>
> Travis CI hit this error testing commit 853f8ca13cd6d256:
>
> $ clang --version
> Apple LLVM version 8.1.0 (clang-802.0.42)
> Target: x86_64-apple-darwin16.7.0
>
> $ ./configure
> C compiler clang
> host CPU x86_64
> ...
> TPM support yes
> libssh2 support no
> TPM passthrough no
> TPM emulator yes
>
> GTESTER check-qtest-i386
> Unexpected error in qio_channel_socket_readv() at io/channel-socket.c:494:
> **
> ERROR:tests/tpm-emu.c:27:tpm_emu_test_wait_cond: code should not be reached
> make: *** [check-qtest-i386] Error 1
> make: *** Waiting for unfinished jobs....
This test has a couple of threads running, and passes &error_abort to
the qio_channel_socket_readv() function. So I expect that one thread
is closing the socket connection, and the other thread has not yet
shutdown cleanly, so tries to readv on a dead socket triggering the
error_abort. IOW, qio_channel_socket_readv is likely just the symptom
of brokeness somewhere else in the test, not the cause.
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:[~2018-05-08 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 12:41 [Qemu-devel] tpm_emu_test_wait_cond: code should not be reached Philippe Mathieu-Daudé
2018-05-08 13:41 ` Peter Maydell
2018-05-08 13:48 ` Daniel P. Berrangé [this message]
2018-05-08 13:54 ` Peter Maydell
2018-05-08 14:03 ` Daniel P. Berrangé
2018-05-08 15:18 ` Stefan Berger
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=20180508134831.GV5967@redhat.com \
--to=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.com \
/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.