From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] glib-compat: work around g_test_message bug with subprocess tests
Date: Fri, 30 Nov 2018 11:03:54 +0100 [thread overview]
Message-ID: <d2c9486a-e05b-b62e-d9d1-65a2b022c4d2@redhat.com> (raw)
In-Reply-To: <20181130095830.GD8101@redhat.com>
On 30/11/18 10:58, Daniel P. Berrangé wrote:
> On Fri, Nov 30, 2018 at 01:08:29AM +0100, Paolo Bonzini wrote:
>> On 29/11/18 19:00, Paolo Bonzini wrote:
>>> Subprocesses are created by glib without leaving the file descriptors
>>> open. Therefore, g_test_message (and assertion failures, but those
>>> trigger when things are going bad anyway) will think that it is writing
>>> to the log file descriptor, but while actually stomping on the QMP
>>> file descriptor or similar. This causes spurious failures, which are
>>> as nice to debug as the reader can imagine. While I have opened a
>>> pull request on GLib, this will probably take a while to propagate
>>> to distros.
>>>
>>> I found this while working on qgraph, but the fix is generic.
>>
>> This is not a problem anymore if we switch from gtester to tap. Do we
>> want it fixed anyway or not?
>
> IMHO the change to tap is not really something we shoudl be doing
> at this point in the release cycle.
Of course---I wasn't suggesting that, the TAP switch is for 4.0.
However, this fix is not needed for 3.1 as far as I know, and we're
pretty late in 3.1's rc period too.
Paolo
> So I'd favour taking this fix
> for 3.1, even if it becomes redundant when we switch to tap in 4.0
prev parent reply other threads:[~2018-11-30 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 18:00 [Qemu-devel] [PATCH v2] glib-compat: work around g_test_message bug with subprocess tests Paolo Bonzini
2018-11-30 0:08 ` Paolo Bonzini
2018-11-30 0:58 ` Eric Blake
2018-11-30 9:58 ` Daniel P. Berrangé
2018-11-30 10:03 ` Paolo Bonzini [this message]
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=d2c9486a-e05b-b62e-d9d1-65a2b022c4d2@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@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).