From: Igor Mammedov <imammedo@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
qemu-trivial@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH for-2.11] tests/bios-tables: Silence some messages with V=1, print them with V=2 only
Date: Wed, 30 Aug 2017 15:48:03 +0200 [thread overview]
Message-ID: <20170830154803.46bc99fc@nial.brq.redhat.com> (raw)
In-Reply-To: <1503941985-25657-1-git-send-email-thuth@redhat.com>
On Mon, 28 Aug 2017 19:39:45 +0200
Thomas Huth <thuth@redhat.com> wrote:
> When running "make check-qtest-x86_64 V=1", the output is currently flooded
> with "Looking for expected file ..." and "Using expected file ..." messages.
> None of the other tests is doing that with V=1, so this is a little bit
> annoying. Let's only print these debug messages when we're running the test
> with V=2 or higher.
well, normally make check is run without V=
and if someone once in a while need to run it in verbose mode,
he/she can tolerate it since it's a verbose mode after all.
Hiding message behind V=XX is going to make us remember/recall
at which verbosity level one needs to run tests to get needed
diagnostic info.
I'd rather keep it as it is now.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> tests/bios-tables-test.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/tests/bios-tables-test.c b/tests/bios-tables-test.c
> index 564da45..289ee45 100644
> --- a/tests/bios-tables-test.c
> +++ b/tests/bios-tables-test.c
> @@ -40,6 +40,7 @@ typedef struct {
> int required_struct_types_len;
> } test_data;
>
> +static bool really_verbose;
> static char disk[] = "tests/acpi-test-disk-XXXXXX";
> static const char *data_dir = "tests/acpi-test-data";
> #ifdef CONFIG_IASL
> @@ -395,7 +396,7 @@ static GArray *load_expected_aml(test_data *data)
> try_again:
> aml_file = g_strdup_printf("%s/%s/%.4s%s", data_dir, data->machine,
> (gchar *)&signature, ext);
> - if (getenv("V")) {
> + if (really_verbose) {
> fprintf(stderr, "\nLooking for expected file '%s'\n", aml_file);
> }
> if (g_file_test(aml_file, G_FILE_TEST_EXISTS)) {
> @@ -407,7 +408,7 @@ try_again:
> goto try_again;
> }
> g_assert(exp_sdt.aml_file);
> - if (getenv("V")) {
> + if (really_verbose) {
> fprintf(stderr, "\nUsing expected file '%s'\n", aml_file);
> }
> ret = g_file_get_contents(aml_file, &exp_sdt.aml,
> @@ -812,6 +813,11 @@ int main(int argc, char *argv[])
> {
> const char *arch = qtest_get_arch();
> int ret;
> + const char *v_env = getenv("V");
> +
> + if (v_env && *v_env >= '2') {
> + really_verbose = true;
> + }
>
> ret = boot_sector_init(disk);
> if(ret)
next prev parent reply other threads:[~2017-08-30 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 17:39 [Qemu-trivial] [PATCH for-2.11] tests/bios-tables: Silence some messages with V=1, print them with V=2 only Thomas Huth
2017-08-30 13:48 ` Igor Mammedov [this message]
2017-08-31 13:35 ` [Qemu-trivial] [Qemu-devel] " Thomas Huth
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=20170830154803.46bc99fc@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).