On 08/02/2018 22:54, Alistair Francis wrote:
> On Thu, Feb 8, 2018 at 1:12 PM, Peter Maydell <peter.mayd...@linaro.org>
>> On 8 February 2018 at 19:13, Thomas Huth <th...@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
> 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.