[LTP] [Valgrind-developers] [RFC PATCH 1/1] LTP tests: Run without LTP_REPRODUCIBLE_OUTPUT=1

Martin Cermak mcermak@redhat.com
Wed Mar 25 11:01:30 CET 2026


On  Wed  2026-03-25  10:57 , Cyril Hrubis wrote:
> Hi!
> > > > That sounds reasonable to me.  Which one would you prefer to
> > > > keep?  I'm inclined to suggest keeping LTP_REPRODUCIBLE_OUTPUT
> > > > and dropping LTP_QUIET but no really strong preference on my
> > > > side.  Thoughts?
> > > 
> > > Maybe we can finally implement proper debug levels in LTP. E.g. hide
> > > TINFO and TWARN messages with debug level 0 and default to debug level
> > > 1. With debug level 2 we would show TDEBUG as well and with debug level
> > > 3 we would show TDEBUG messages for library too.
> > 
> > That would require running valgrind tests with something like
> > debug level -1 ;) because what LTP_REPRODUCIBLE_OUTPUT actually
> > does is that it hides testrun specific output like e.g. testrun
> > specific addresses, temporary file names etc.
> 
> The LTP_REPRODUCIBLE_OUTPUT would have to stay, but the LTP_QUITE would
> have been replaced by different debug levels.

That sounds like a good approach to me, yup.

m.



More information about the ltp mailing list