From: Cyril Hrubis <chrubis@suse.cz>
To: Martin Cermak <mcermak@redhat.com>
Cc: Mark Wielaard <mark@klomp.org>, ltp@lists.linux.it
Subject: Re: [LTP] LTP in valgrind :)
Date: Wed, 7 May 2025 17:29:00 +0200 [thread overview]
Message-ID: <aBt8PJNmiJNuSEB5@yuki.lan> (raw)
In-Reply-To: <20250507151148.yhrnckco7zkrpfzw@lida.tpb.lab.eng.brq.redhat.com>
Hi!
> > > > > It also opens some interesting questions, i.e. how do we make comparing
> > > > > results from two different tests easier. Currently they grep the test
> > > > > results for a summary, but maybe we can do better.
> >
> > > > One option is to extract all TPASS/TFAIL/TWARN/TBROK/TCONF messages,
> > > > discard any message contents past the file:line header and then compare
> > > > whether the sanitized output is identical. That'll take care of random
> > > > values in the output while ensuring that the test went through the same
> > > > code paths as before. We could provide a sanitizer script for that.
> >
> > > Maybe we can even add an option to the test library to supress the
> > > messages in output, that would be fairly simple.
> >
> > @Martin @Mark: feel free to comment what we can do for you :).
> > Whole thread:
> > https://lore.kernel.org/ltp/20250505195003.GB137650@pevik/T/#t
>
> Nice to see you noticed! Primarily we're trying to identify
> valgrind gaps and bugs. For our use-case it's good to have
> reproducible test runs in a sense of identical test results for
> repeated test runs. We got pretty close to this by only taking
> into account the testcase summaries at the very end of the test
> logs. Any steps to get closer to reproducible test runs on the
> LTP side are interesting for us, and we'll try to reflect those!
I've proposed a simple solution that would cut the message from tests
only to contain the line numbers and results in:
https://lore.kernel.org/ltp/20250505195003.GB137650@pevik/T/#m98317262b25ede62704b005fcefc63c62198bb90
If that works for you we can get this in LTP before the next release.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-05-07 15:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 5:22 [LTP] LTP in valgrind :) Petr Vorel
2025-04-29 6:59 ` Andrea Cervesato via ltp
2025-05-02 9:49 ` Cyril Hrubis
2025-05-02 10:53 ` Martin Doucha
2025-05-05 8:57 ` Cyril Hrubis
2025-05-05 19:52 ` Petr Vorel
2025-05-06 8:05 ` Petr Vorel
2025-05-07 15:11 ` Martin Cermak via ltp
2025-05-07 15:29 ` Cyril Hrubis [this message]
2025-05-08 16:07 ` Mark Wielaard
2025-05-09 8:24 ` Cyril Hrubis
2025-05-09 14:16 ` Bird, Tim
2025-05-12 8:09 ` Cyril Hrubis
2025-05-08 16:40 ` Mark Wielaard
2025-05-05 19:50 ` Petr Vorel
2025-05-06 8:03 ` Cyril Hrubis
2025-05-06 8:25 ` 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=aBt8PJNmiJNuSEB5@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mark@klomp.org \
--cc=mcermak@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