From: klim <klim.kireev@virtuozzo.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Alistair Francis <alistair23@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Denis V. Lunev" <den@virtuozzo.com>
Subject: Re: [Qemu-devel] "make check -j4" hangs
Date: Mon, 12 Feb 2018 17:42:41 +0300 [thread overview]
Message-ID: <ac7cca9f-24f7-6b04-acbd-e63c99df9136@virtuozzo.com> (raw)
In-Reply-To: <4b726592-1078-1ac8-37b1-9227122d2429@redhat.com>
On 02/09/2018 02:55 PM, Paolo Bonzini wrote:
> On 08/02/2018 22:54, Alistair Francis wrote:
>> On Thu, Feb 8, 2018 at 1:12 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
>>> On 8 February 2018 at 19:13, Thomas Huth <thuth@redhat.com> wrote:
>>>> I'm currently facing some issues with "make check -j4" (i.e. running the
>>>> tests in parallel). Git bisect blames this commit - though I'm not sure
>>>> whether this is really the right one ... Starting with this commit, I
>>>> saw hangs in test-filter-redirector, but git master rather seems to hang
>>>> with vhost-user-test instead.
>>>> Stefan also had issues with "make check -j4" today, so it's apparently
>>>> not only me ... can somebody else reproduce the problem with the git
>>>> master branch?
>>> Yeah, I was seeing odd make check hangs with parallelization enabled
>>> too, on vhost-user-test... (my builds for merge tests are almost
>>> all non-parallelized I think).
>> I don't only see hangs I also am seeing this:
>>
>> qemu-system-i386: -chardev
>> socket,id=chr-test,path=/tmp/vhost-test-wxuOIX/test.sock: Failed to
>> connect socket /tmp/vhost-test-wxuOIX/test.sock: No such file or
>> directory
>> socket_accept failed: Resource temporarily unavailable
>> **
>> ERROR:tests/libqtest.c:218:qtest_init_without_qmp_handshake: assertion
>> failed: (s->fd >= 0 && s->qmp_fd >= 0)
>> GTester: last random seed: R02Sa67ba85090274c01deb9c2d15b044c10
>>
>> It isn't 100% reproducible though.
> It may be something like commit 8f6d701044bc87197aac8aa2a627d70ce8471726.
>
> In the meanwhile we should revert it.
>
> Paolo
I just have reverted my 2 commits and
after that make check -j32 hangs
with
GTester: last random seed: R02Sb95a3bf6ab4c05540cec188081a7cc2a
in vhost-user-test
so it is not my fault
next prev parent reply other threads:[~2018-02-12 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 13:51 [Qemu-devel] [PATCH v5] chardev/char-socket: add POLLHUP handler Klim Kireev
2018-01-30 19:49 ` Paolo Bonzini
2018-02-08 19:13 ` [Qemu-devel] "make check -j4" hangs (was: Re: chardev/char-socket: add POLLHUP handler) Thomas Huth
2018-02-08 21:12 ` Peter Maydell
2018-02-08 21:54 ` Alistair Francis
2018-02-09 11:55 ` [Qemu-devel] "make check -j4" hangs Paolo Bonzini
2018-02-12 14:42 ` klim [this message]
2018-02-12 19:30 ` Thomas Huth
2018-02-12 22:14 ` Paolo Bonzini
2018-02-13 11:21 ` Peter Maydell
2018-02-09 12:47 ` Klim Kireev
2018-02-09 16:03 ` Thomas Huth
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=ac7cca9f-24f7-6b04-acbd-e63c99df9136@virtuozzo.com \
--to=klim.kireev@virtuozzo.com \
--cc=alistair23@gmail.com \
--cc=den@virtuozzo.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.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 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).