All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: valgrind-developers@lists.sourceforge.net,
	Martin Cermak <mcermak@redhat.com>,
	ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH 1/1] LTP tests: Run without LTP_REPRODUCIBLE_OUTPUT=1
Date: Tue, 24 Mar 2026 14:18:11 +0100	[thread overview]
Message-ID: <acKPE_1MwQhayd4O@yuki.lan> (raw)
In-Reply-To: <20260323210805.20929-1-pvorel@suse.cz>

Hi!
> 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. Therefore LTP_REPRODUCIBLE_OUTPUT=1 is not
> needed any more.

I do not think so. We still have things like pids and timestamps in
TPASS/TFAIL messages that needs to be removed in order for the output to
be reproducible.

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2026-03-24 13:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 21:08 [LTP] [RFC PATCH 1/1] LTP tests: Run without LTP_REPRODUCIBLE_OUTPUT=1 Petr Vorel
2026-03-24 13:18 ` Cyril Hrubis [this message]
2026-03-24 14:09   ` [LTP] [Valgrind-developers] " Martin Cermak via ltp
2026-03-25  9:06     ` Martin Cermak via ltp
2026-03-25  9:10       ` Petr Vorel
2026-03-25  9:21         ` Martin Cermak via ltp
2026-03-25  9:37           ` Cyril Hrubis
2026-03-25  9:42             ` Martin Cermak via ltp
2026-03-25  9:57               ` Cyril Hrubis
2026-03-25 10:01                 ` Martin Cermak via ltp
2026-03-25 13:57                 ` Petr Vorel
2026-03-25 14:52                   ` Martin Cermak via ltp
2026-03-26 16:42                     ` Petr Vorel

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=acKPE_1MwQhayd4O@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=mcermak@redhat.com \
    --cc=pvorel@suse.cz \
    --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.