All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Martin Cermak <mcermak@redhat.com>
Cc: valgrind-developers@lists.sourceforge.net,
	Mark Wielaard <mark@klomp.org>,
	ltp@lists.linux.it
Subject: Re: [LTP] Proposal for new LTP config knob: LTP_QUIET
Date: Wed, 17 Sep 2025 13:30:13 +0200	[thread overview]
Message-ID: <20250917113013.GA340479@pevik> (raw)
In-Reply-To: <20250917111319.wgfpjmkicmv2rjti@lida.tpb.lab.eng.brq.redhat.com>

> On  Wed  2025-09-17  12:37 , Petr Vorel wrote:
> > Hi Martin,

> > > Hi folks,

> > > some time back, LTP_REPRODUCIBLE_OUTPUT was introduced in LTP.
> > > I'd like to propose a new, related LTP knob for our Valgrind
> > > test automation purposes: LTP_QUIET.  See attached patch.

> > > LTP_QUIET is supposed to suppress certain types of test output
> > > messages, such as: TCONF, TWARN, TINFO, and TDEBUG.  This would
> > > help us keep our test logs briefer, while still keeping the
> > > information we need in the logs.

> > > Please, consider merging upstream.

> > Thanks for contributing this. So the point is to have only the final summary
> > printed, right? (summary of TCONF/TWARN/TBROK/...).

> > I'm ok for merging this + to introduce the same for shell API (tst_test.sh),
> > although you in valgrind don't use it.  And we could even introduce '-q' getopt
> > (easier for manual debugging).

> > Do we then want to keep the "reproducible output" part? Or should it quiet
> > replace it?

> Hi Petr,  you are right that these two knobs (LTP_QUIET and
> LTP_REPRODUCIBLE_OUTPUT) partly overlap.  In my proposal, LTP_QUIET
> doesn't silence everything.  It does silence TCONF, TWARN, TINFO,
> and TDEBUG messages.  But it keeps TPASS, TFAIL, and TBROK.

Ah, correct (I was wrong). If there were users who need to separate these (i.e.
using just single of these) I would keep it separate. But IMHO you valgrind
folks are the only ones who use it, therefore feel free to modify it to fix your
needs. OTOH, if you're ok to using 2 variables, I guess we are ok to have both.
Let's see what others think (Andrea already acked).

> Suppressing everything except the final summary seemed too
> aggressive to me initially.  But as we speak, it would work for
> Valgrind testing purposes just fine.

If you compare whole output mismatch in Summary would catch a difference.

OTOH you're right that it's safer to keep at least TFAIL and TBROK.
I'd personally add also TWARN (not that many messages).

Kind regards,
Petr

> > @Cyril, if you agree, do we dare to have it before the release?



-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-09-17 11:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17  9:07 [LTP] Proposal for new LTP config knob: LTP_QUIET Martin Cermak via ltp
2025-09-17 10:37 ` Petr Vorel
2025-09-17 11:13   ` Martin Cermak via ltp
2025-09-17 11:30     ` Petr Vorel [this message]
2025-09-17 11:36       ` Martin Cermak via ltp
2025-09-17 11:13   ` Andrea Cervesato via ltp
2025-09-22  8:01 ` Cyril Hrubis
2025-09-22 11:06   ` Martin Cermak via ltp
2025-09-29 10:46     ` Cyril Hrubis
2025-09-29 10:52       ` Martin Cermak via ltp

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=20250917113013.GA340479@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=mark@klomp.org \
    --cc=mcermak@redhat.com \
    --cc=valgrind-developers@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.