From: Fam Zheng <famz@redhat.com>
To: Patchew Tool <patchew.tool@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4] hmp: add info iothreads command
Date: Fri, 13 Mar 2015 17:30:41 +0800 [thread overview]
Message-ID: <20150313093041.GF3527@ad.nay.redhat.com> (raw)
In-Reply-To: <5502aaee.510f370a.4bed.5182@mx.google.com>
On Fri, 03/13 02:16, Patchew Tool wrote:
> socket_accept failed: Resource temporarily unavailable
> **
> ERROR:/var/tmp/patchew-test/git/tests/libqtest.c:192:qtest_init: assertion failed: (s->fd >= 0 && s->qmp_fd >= 0)
> GTester: last random seed: R02Sa6e2a5d48f79c1916f52824e1b74ecc5
> socket_accept failed: Resource temporarily unavailable
> **
> ERROR:/var/tmp/patchew-test/git/tests/libqtest.c:192:qtest_init: assertion failed: (s->fd >= 0 && s->qmp_fd >= 0)
> GTester: last random seed: R02Sd05e2b63284437ca347a3e639d127a65
> blkdebug: Suspended request 'A'
> blkdebug: Resuming request 'A'
> main-loop: WARNING: I/O thread spun for 1000 iterations
> main-loop: WARNING: I/O thread spun for 1000 iterations
> main-loop: WARNING: I/O thread spun for 1000 iterations
> main-loop: WARNING: I/O thread spun for 1000 iterations
> [vmxnet3][WR][vmxnet3_peer_has_vnet_hdr]: Peer has no virtio extension. Task offloads will be emulated.
> make: *** [check-qtest-x86_64] Error 1
Hmm.. looks like a false alarm, the socket initialization failed but that's
definitely not related to this patch.
Fam
next prev parent reply other threads:[~2015-03-13 9:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 8:58 [Qemu-devel] [PATCH v4] hmp: add info iothreads command Ting Wang
2015-03-13 9:10 ` Fam Zheng
2015-03-13 9:16 ` Patchew Tool
2015-03-13 9:30 ` Fam Zheng [this message]
2015-03-13 14:09 ` Markus Armbruster
2015-03-17 15:48 ` Stefan Hajnoczi
2015-06-23 2:22 ` Ting Wang
2015-06-23 11:57 ` Markus Armbruster
2015-06-23 12:19 ` Christian Borntraeger
2015-06-23 12:31 ` Christian Borntraeger
2015-06-23 15:02 ` Stefan Hajnoczi
2015-06-23 13:47 ` Luiz Capitulino
2015-06-26 6:15 ` Ting Wang
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=20150313093041.GF3527@ad.nay.redhat.com \
--to=famz@redhat.com \
--cc=patchew.tool@gmail.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).