qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Eduardo Habkost" <ehabkost@redhat.com>,
	"Marc-André Lureau" <mlureau@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] vhost-user-test failure
Date: Mon, 26 Sep 2016 14:52:21 +0200	[thread overview]
Message-ID: <3c623e89-3a46-d77b-c352-834da483531f@redhat.com> (raw)
In-Reply-To: <20160926121331.GF3877@thinpad.lan.raisama.net>

Hi,

On 09/26/2016 02:13 PM, Eduardo Habkost wrote:
> On Sun, Sep 25, 2016 at 04:55:53PM -0400, Marc-André Lureau wrote:
>> Hi
>>
>> ----- Original Message -----
>>> This time with Marc-André in cc:...
>>>
>>> On 09/23/2016 07:40 PM, Maxime Coquelin wrote:
>>>>
>>>>
>>>> On 09/23/2016 05:41 PM, Michael S. Tsirkin wrote:
>>>>> 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?
>>>> No, not really.
>>>> Marc-André contributed a lot to these tests, I add him in cc: in case
>>>> he has an idea.
>>>>
>>>> I will have a look in the mean time.
>>>>
>>
>> I am unable to reproduce locally (over 500x iterations), and I
>> have no clue what's going on: the warnings there aren't the
>> problem (that's the main reason why we use the subprocess, to
>> silence those). Do you have a local reproducer or is it only on
>> travis? Afaik, there are no other reports of this test failing,
>> are you sure its not related to changes on your branch?
>
> I don't have a local reproducer, I could only see it once on
> travis-ci. Maybe it is not possible to reproduce it if the
> machine isn't loaded enough to make the right thread/process be
> delayed.

I'm also trying to reproduce it.
Interestingly, launching the test with strace, I reproduce another
problem systematically:
$> strace -o /tmp/vut -ff ./tests/vhost-user-test
/x86_64/vhost-user/read-guest-mem: OK
/x86_64/vhost-user/migrate: Vhost user backend fails to broadcast fake RARP
OK
/x86_64/vhost-user/reconnect: OK

I'll try to load the CPU randomly when executing the test.

Regards,
Maxime

  reply	other threads:[~2016-09-26 12:52 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
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 [this message]
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=3c623e89-3a46-d77b-c352-834da483531f@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mlureau@redhat.com \
    --cc=mst@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 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).