From: Petr Vorel <pvorel@suse.cz>
To: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.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: Mon, 31 Jan 2022 08:21:13 +0100 [thread overview]
Message-ID: <YfeN6fG28AVNC44n@pevik> (raw)
In-Reply-To: <61F609C7.1080803@fujitsu.com>
...
> > +++ b/lib/tst_test.c
> > @@ -811,6 +811,9 @@ static void do_exit(int ret)
> > fprintf(stderr, "broken %d\n", results->broken);
> > fprintf(stderr, "skipped %d\n", results->skipped);
> > fprintf(stderr, "warnings %d\n", results->warnings);
> > + fprintf(stderr, "not run %d\n", tst_test->tcnt -
> > + results->passed - results->failed - results->broken -
> > + results->skipped - results->warnings);
> IMO, these values are not necessary related. Refer to quotactl01.c(
> tst_test->tcnt is less than results->passed)
Ah, correct. Also .test_all means tst_test->tcnt to be 0.
So my patch is utterly wrong.
> Also, if you want to add a new tag, you should define the situation for it.
What is my point: number of the defined tests does not mean they are all run.
Maybe printing number of the tests in the test (tst_test->tcnt or 1 when
tst_test->test_all)?
My point is to have an idea without looking into the code know how many tests
have been skipped on certain setup.
Kind regards,
Petr
> Best Regards
> Yang Xu
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-31 7:21 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 [this message]
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
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=YfeN6fG28AVNC44n@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=xuyang2018.jy@fujitsu.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