From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <wangli.ahau@gmail.com>
Cc: ltp@lists.linux.it, Martin Cermak <mcermak@redhat.com>
Subject: Re: [LTP] [PATCH v4 5/5] lib: Merge functionality of LTP_QUIET into LTP_REPRODUCIBLE_OUTPUT
Date: Thu, 23 Apr 2026 10:15:31 +0200 [thread overview]
Message-ID: <20260423081531.GA646798@pevik> (raw)
In-Reply-To: <CANgNiRygF3v7V3jAPJ10J+FW1-0fTQf4pq08jJSo8gtKHWmkZQ@mail.gmail.com>
Hi Li,
> Hi Petr,
> Petr Vorel <pvorel@suse.cz> wrote:
> > LTP_REPRODUCIBLE_OUTPUT=1 environment variable was added in 5894abc5f to
> > help valgrind to use LTP for testing. It discards the actual content of
> > the messages printed by the test (removes everything after printing
> > TINFO/TPASS/TFAIL/... flag).
> > Later LTP_QUIET=1 was added which suppresses printing TCONF, TWARN,
> > TINFO, and TDEBUG messages.
> In this patch, I didn't find that it suppresses TWARN messages.
> Should we add it as well?
Thanks to catch this! I'd keep it, it can have valuable info.
> > Valgrind project uses both variables but no need to handle them
> > separately. Therefore merge functionality of LTP_QUIET into
> > LTP_REPRODUCIBLE_OUTPUT.
...
> > +++ b/lib/tst_test.c
> > break;
...
> > @@ -676,8 +675,8 @@ static void print_help(void)
> > fprintf(stderr, "LTP_DEV Path to the block device to be used (for .needs_device)\n");
> > fprintf(stderr, "LTP_DEV_FS_TYPE Filesystem used for testing (default: %s)\n", DEFAULT_FS_TYPE);
> > fprintf(stderr, "LTP_DEBUG Print debug messages (set 1(y) or 2)\n");
> > - fprintf(stderr, "LTP_REPRODUCIBLE_OUTPUT Values 1 or y discard the actual content of the messages printed by the test\n");
> > - fprintf(stderr, "LTP_QUIET Values 1 or y will suppress printing TCONF, TWARN, TINFO, and TDEBUG messages\n");
> > + fprintf(stderr, "LTP_REPRODUCIBLE_OUTPUT Values 1 or y suppress printing TCONF, TWARN, TINFO, and TDEBUG messages and");
> > + fprintf(stderr, " discards the actual content of all other messages");
> I guess this two-line format is a bit strange when printing.
> Maybe we need to combine into a single fprintf()?
OK, but I'd split new line. + Add \n as AI found :).
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-04-23 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 14:12 [LTP] [PATCH v4 0/5] lib: LTP_DEBUG cleanup Petr Vorel
2026-04-22 14:12 ` [LTP] [PATCH v4 1/5] lib: Ignore empty LTP_ENABLE_DEBUG Petr Vorel
2026-04-22 15:18 ` [LTP] " linuxtestproject.agent
2026-04-22 14:12 ` [LTP] [PATCH v4 2/5] lib: Rename variable LTP_ENABLE_DEBUG => LTP_DEBUG Petr Vorel
2026-04-22 14:12 ` [LTP] [PATCH v4 3/5] lib: Prefer LTP_DEBUG over -D Petr Vorel
2026-04-23 6:43 ` Li Wang
2026-04-22 14:12 ` [LTP] [PATCH v4 4/5] doc: newlib_tests: Update debugging parameters Petr Vorel
2026-04-23 6:45 ` Li Wang
2026-04-22 14:12 ` [LTP] [PATCH v4 5/5] lib: Merge functionality of LTP_QUIET into LTP_REPRODUCIBLE_OUTPUT Petr Vorel
2026-04-23 7:09 ` Li Wang
2026-04-23 8:15 ` Petr Vorel [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=20260423081531.GA646798@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mcermak@redhat.com \
--cc=wangli.ahau@gmail.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