From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>, Fabiano Rosas <farosas@suse.de>,
qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>
Subject: Re: [RFC PATCH 0/2] qtest: Log verbosity changes
Date: Fri, 13 Sep 2024 12:56:26 +0100 [thread overview]
Message-ID: <ZuQoauSdVNaG3F6m@redhat.com> (raw)
In-Reply-To: <CAFEAcA-naWfN5sLSJ3uS6VjC3HWvyaGqAk0=B_iqTYgtJOH+ow@mail.gmail.com>
On Fri, Sep 06, 2024 at 10:52:53AM +0100, Peter Maydell wrote:
> On Fri, 6 Sept 2024 at 09:14, Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > On Fri, Sep 06, 2024 at 08:16:31AM +0200, Thomas Huth wrote:
> > > On 05/09/2024 23.03, Fabiano Rosas wrote:
> > > > Hi,
> > > >
> > > > This series silences QEMU stderr unless the QTEST_LOG variable is set
> > > > and silences -qtest-log unless both QTEST_LOG and gtest's --verbose
> > > > flag is passed.
> > > >
> > > > This was motivated by Peter Maydell's ask to suppress deprecation
> > > > warn_report messages from the migration-tests and by my own
> > > > frustration over noisy output from qtest.
>
> This isn't what I want, though -- what I want is that a
> qtest run should not print "warning:" messages for things
> that we expect to happen when we run that test. I *do* want
> warnings for things that we do not expect to happen when
> we run the test.
Currently we just allow the child QEMU process stdout/err
to inherit to the qtest program's stdout/err. With that
approach we have to do filtering at soruce (ie in QEMU
itself). I feel that in general it is a bad idea for the
program being tested to alter itself to suit the test
suite, not least because two different parts of the test
suite may have differing views about what messages they
want to ignore vs display.
We could address this be switching to the model used
with IO tests. Always capture the child QEMU process
stdout/err to a pipe. The test program can apply regex
filters to cull output that is expected & irrelevant,
and then print out whatever is left over on its own
stderr.
That way all the filtering of undesirable messages would
be exclusively in the test suite, not QEMU itself.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-09-13 11:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 21:03 [RFC PATCH 0/2] qtest: Log verbosity changes Fabiano Rosas
2024-09-05 21:03 ` [RFC PATCH 1/2] tests/qtest: Mute QEMU stderr Fabiano Rosas
2024-09-05 21:03 ` [RFC PATCH 2/2] tests/qtest: Mute -qtest-log Fabiano Rosas
2024-09-06 6:16 ` [RFC PATCH 0/2] qtest: Log verbosity changes Thomas Huth
2024-09-06 8:14 ` Daniel P. Berrangé
2024-09-06 9:52 ` Peter Maydell
2024-09-06 14:42 ` Fabiano Rosas
2024-09-13 10:02 ` Markus Armbruster
2024-09-13 10:08 ` Peter Maydell
2024-09-13 11:29 ` Markus Armbruster
2024-09-13 11:46 ` Peter Maydell
2024-09-13 12:14 ` Thomas Huth
2024-09-13 11:56 ` Daniel P. Berrangé [this message]
2024-09-14 9:35 ` Markus Armbruster
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=ZuQoauSdVNaG3F6m@redhat.com \
--to=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).