From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, maxime.coquelin@redhat.com
Subject: Re: [Qemu-devel] vhost-user-test failure
Date: Fri, 23 Sep 2016 18:41:03 +0300 [thread overview]
Message-ID: <20160923184040-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20160923153612.GU3233@thinpad.lan.raisama.net>
On Fri, Sep 23, 2016 at 12:36:12PM -0300, Eduardo Habkost wrote:
> Hi,
>
> I hit a weird vhost-user-test failure on travis-ci recently, on a
> branch where I didn't touch any vhost-related code. From a quick
> look at the code, it looks like the vhost-user code is unhappy to
> see a disconnected socket.
>
> I wasn't able to reproduce it. It seems to be a hard to reproduce
> race between vhost-user code and socket reconnection.
>
> The failure can be seen at:
>
> https://travis-ci.org/ehabkost/qemu-hacks/jobs/162077239
Maxime looked at something similiar. Any idea?
> Error output:
>
> **
> ERROR:tests/vhost-user-test.c:715:test_reconnect: child process (/i386/vhost-user/reconnect/subprocess [23792]) failed unexpectedly
> qemu-system-i386: Failed to set msg fds.
> qemu-system-i386: vhost VQ 0 ring restore failed: -1: Resource temporarily unavailable (11)
> qemu-system-i386: Failed to set msg fds.
> qemu-system-i386: vhost VQ 1 ring restore failed: -1: Resource temporarily unavailable (11)
> GTester: last random seed: R02S2892f6ad84bd5d03acd54cb75f444243
> make: *** [check-qtest-i386] Error 1
>
> --
> Eduardo
next prev parent reply other threads:[~2016-09-23 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 15:36 [Qemu-devel] vhost-user-test failure Eduardo Habkost
2016-09-23 15:41 ` Michael S. Tsirkin [this message]
2016-09-23 17:40 ` Maxime Coquelin
2016-09-24 17:42 ` Maxime Coquelin
2016-09-25 20:55 ` Marc-André Lureau
2016-09-26 12:13 ` Eduardo Habkost
2016-09-26 12:52 ` Maxime Coquelin
2016-09-26 14:07 ` Maxime Coquelin
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=20160923184040-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ehabkost@redhat.com \
--cc=maxime.coquelin@redhat.com \
--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.