From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: Petr Vorel <pvorel@suse.cz>
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: Sun, 30 Jan 2022 03:44:25 +0000 [thread overview]
Message-ID: <61F609C7.1080803@fujitsu.com> (raw)
In-Reply-To: <20220127171455.9809-1-pvorel@suse.cz>
Hi Petr
> We count only tests which TCONF. In case tst_brk() some tests might be
> skipped without even trying to run them), thus print them.
>
> Signed-off-by: Petr Vorel<pvorel@suse.cz>
> ---
> Hi,
>
> probably quite confusing to have "skipped" and "not run".
> Maybe rename s/skipped/cancelled/ and s/not run/skipped/ ?
> Or just to increase cound of skipped?
>
> E.g. instead of:
>
> bind05.c:132: TCONF: socket(10, 2, 0) failed: EAFNOSUPPORT (97)
>
> Summary:
> passed 8
> failed 0
> broken 0
> skipped 1
> warnings 0
> not run 5
>
> have
> bind05.c:132: TCONF: socket(10, 2, 0) failed: EAFNOSUPPORT (97)
>
> Summary:
> passed 8
> failed 0
> broken 0
> skipped 6
> warnings 0
>
> Kind regards,
> Petr
>
> lib/tst_test.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/lib/tst_test.c b/lib/tst_test.c
> index 844756fbd7..e5ea9e6165 100644
> --- a/lib/tst_test.c
> +++ 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)
Also, if you want to add a new tag, you should define the situation for it.
Best Regards
Yang Xu
> }
>
> do_cleanup();
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-30 3:44 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 [this message]
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
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=61F609C7.1080803@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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