From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [RFC PATCH 1/1] lib: Print in summary also tests not run at all
Date: Thu, 10 Feb 2022 17:31:26 +0100 [thread overview]
Message-ID: <YgU93mtJnqeTZPv3@pevik> (raw)
In-Reply-To: <CAEemH2cHe-Mc9g=ScTH5F0c5_WmrvsvHSObsDVy0aa-ayz76zA@mail.gmail.com>
> On Wed, Feb 9, 2022 at 8:53 PM Petr Vorel <pvorel@suse.cz> wrote:
> > Hi Li, Xu,
> > > > In fact, we don't have mandatory rules that TAPSS or TFAIL only can
> > > > occur one time. a example ie memcontrol02.c
> > > Right, that is my hesitant part for counting that.
> > > Seems many tests abuse the TPASS|TFAIL for defining test fail bound.
> > OK, while it'd be useful for some tests, it'd be confusing due this for
> > other.
> > I guess printing (tst_test->tcnt * test_variants) number can be confusing
> > either.
> Agree, so we might need more time coming up with a better solution.
> Or, we go another way to limit the abuse in TPASS|TFAIL in the test.
> But both sound not easy at this moment.
Given number of the tests we have (and how many of them we need to rewrite)
it'd be hard (and probably not worth of doing it).
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-02-10 16:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 17:14 [LTP] [RFC PATCH 1/1] lib: Print in summary also tests not run at all Petr Vorel
2022-01-30 3:44 ` xuyang2018.jy
2022-01-30 6:09 ` Li Wang
2022-01-30 6:28 ` xuyang
2022-02-02 2:59 ` Li Wang
2022-01-31 7:21 ` Petr Vorel
2022-02-01 13:26 ` Li Wang
2022-02-01 17:39 ` Petr Vorel
2022-02-02 1:40 ` Li Wang
2022-02-02 10:07 ` Petr Vorel
2022-02-07 3:45 ` xuyang2018.jy
2022-02-07 4:09 ` Li Wang
2022-02-09 12:53 ` Petr Vorel
2022-02-10 2:19 ` Li Wang
2022-02-10 16:31 ` 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=YgU93mtJnqeTZPv3@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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