From: John Snow <jsnow@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH 0/3] iotests: enable logging prior to notrun() invocation
Date: Mon, 18 May 2020 14:33:44 -0400 [thread overview]
Message-ID: <afb2eb67-469d-f562-66e9-f2e5bebed8fa@redhat.com> (raw)
In-Reply-To: <20200515095733.GE93011@linux.fritz.box>
On 5/15/20 5:57 AM, Kevin Wolf wrote:
> Am 14.05.2020 um 22:16 hat John Snow geschrieben:
>> Hi, you can take just patch 1.
>
> Thanks, I'm doing that now.
>
>> patches 2-3 admittedly don't do a whole heck of a lot, because I
>> didn't realize that ./check discards *all* output from either stdout
>> or stderr.
>
> It doesn't discard it, but it compares it to the reference output and
> prints a diff if it's non-empty.
>
notrun cases do effectively discard that output, though. I guess that's
fine if it gets logged as output otherwise.
> At least for bash scripts, stderr contains important test output. Not
> sure what the *_log() functions in iotests.py do, maybe they redirect
> the stderr output from tools to stdout.
>
>> The changes are tiny, though, and maybe still worth doing in the long
>> run? Hm. They are archived on the list now, anyway.
>
> We can still take these patches for a later pull request if you think we
> should, though I'm not sure if they are useful given how things actually
> work. I don't have a strong opinion either way (except that I don't want
> to see more than a single line per test without -d, but these patches
> don't try to do this even though you wrote them under the assumption
> that this is how things work).
>
Nah, it's fine. Bigger fish to fry. Thanks!
prev parent reply other threads:[~2020-05-18 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 20:16 [PATCH 0/3] iotests: enable logging prior to notrun() invocation John Snow
2020-05-14 20:16 ` [PATCH 1/3] iotests: log messages from notrun() John Snow
2020-05-14 20:16 ` [PATCH 2/3] iotests: log to stderr instead of stdout John Snow
2020-05-14 20:16 ` [PATCH 3/3] iotests: Categorize NOTRUN messages as INFO, not WARNING John Snow
2020-05-15 9:57 ` [PATCH 0/3] iotests: enable logging prior to notrun() invocation Kevin Wolf
2020-05-18 18:33 ` John Snow [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=afb2eb67-469d-f562-66e9-f2e5bebed8fa@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).