From: Kees Cook <keescook@chromium.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: shuah@kernel.org, luto@amacapital.net, wad@chromium.org,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@fb.com,
Tim.Bird@sony.com
Subject: Re: [PATCH v3 4/6] kselftest: run tests by fixture
Date: Tue, 17 Mar 2020 13:25:53 -0700 [thread overview]
Message-ID: <202003171324.E6E5FE7@keescook> (raw)
In-Reply-To: <20200316225647.3129354-5-kuba@kernel.org>
On Mon, Mar 16, 2020 at 03:56:44PM -0700, Jakub Kicinski wrote:
> Now that all tests have a fixture object move from a global
> list of tests to a list of tests per fixture.
>
> Order of tests may change as we will now group and run test
> fixture by fixture, rather than in declaration order.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> tools/testing/selftests/kselftest_harness.h | 32 +++++++++++++--------
> 1 file changed, 20 insertions(+), 12 deletions(-)
>
> diff --git a/tools/testing/selftests/kselftest_harness.h b/tools/testing/selftests/kselftest_harness.h
> index 0f68943d6f04..36ab1b92eb35 100644
> --- a/tools/testing/selftests/kselftest_harness.h
> +++ b/tools/testing/selftests/kselftest_harness.h
> @@ -660,8 +660,11 @@
> }
>
> /* Contains all the information about a fixture */
> +struct __test_metadata;
> +
Comment should be moved under this (it applies to __fixture_metadata not
__test_metadata).
> struct __fixture_metadata {
> const char *name;
> + struct __test_metadata *tests;
> struct __fixture_metadata *prev, *next;
> } _fixture_global __attribute__((unused)) = {
> .name = "global",
> @@ -696,7 +699,6 @@ struct __test_metadata {
> };
>
> /* Storage for the (global) tests to be run. */
> -static struct __test_metadata *__test_list;
> static unsigned int __test_count;
>
> /*
> @@ -710,8 +712,10 @@ static unsigned int __test_count;
> */
> static inline void __register_test(struct __test_metadata *t)
> {
> + struct __fixture_metadata *f = t->fixture;
> +
> __test_count++;
> - __LIST_APPEND(__test_list, t);
> + __LIST_APPEND(f->tests, t);
Not a big deal, but why not just "f->fixture->tests" here instead of a
separate variable?
> }
>
> static inline int __bail(int for_realz, bool no_print, __u8 step)
> @@ -724,14 +728,15 @@ static inline int __bail(int for_realz, bool no_print, __u8 step)
> return 0;
> }
>
> -void __run_test(struct __test_metadata *t)
> +void __run_test(struct __fixture_metadata *f,
> + struct __test_metadata *t)
> {
> pid_t child_pid;
> int status;
>
> t->passed = 1;
> t->trigger = 0;
> - printf("[ RUN ] %s.%s\n", t->fixture->name, t->name);
> + printf("[ RUN ] %s.%s\n", f->name, t->name);
> alarm(t->timeout);
> child_pid = fork();
> if (child_pid < 0) {
> @@ -781,13 +786,14 @@ void __run_test(struct __test_metadata *t)
> }
> }
> printf("[ %4s ] %s.%s\n", (t->passed ? "OK" : "FAIL"),
> - t->fixture->name, t->name);
> + f->name, t->name);
> alarm(0);
> }
>
> static int test_harness_run(int __attribute__((unused)) argc,
> char __attribute__((unused)) **argv)
> {
> + struct __fixture_metadata *f;
> struct __test_metadata *t;
> int ret = 0;
> unsigned int count = 0;
> @@ -796,13 +802,15 @@ static int test_harness_run(int __attribute__((unused)) argc,
> /* TODO(wad) add optional arguments similar to gtest. */
> printf("[==========] Running %u tests from %u test cases.\n",
> __test_count, __fixture_count + 1);
> - for (t = __test_list; t; t = t->next) {
> - count++;
> - __run_test(t);
> - if (t->passed)
> - pass_count++;
> - else
> - ret = 1;
> + for (f = __fixture_list; f; f = f->next) {
> + for (t = f->tests; t; t = t->next) {
> + count++;
> + __run_test(f, t);
> + if (t->passed)
> + pass_count++;
> + else
> + ret = 1;
> + }
> }
> printf("[==========] %u / %u tests passed.\n", pass_count, count);
> printf("[ %s ]\n", (ret ? "FAILED" : "PASSED"));
> --
> 2.24.1
>
But, with at least the first comment moved:
Acked-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
next prev parent reply other threads:[~2020-03-17 20:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 22:56 [PATCH v3 0/6] kselftest: add fixture parameters Jakub Kicinski
2020-03-16 22:56 ` [PATCH v3 1/6] selftests/seccomp: use correct FIXTURE macro Jakub Kicinski
2020-03-17 20:22 ` Kees Cook
2020-03-16 22:56 ` [PATCH v3 2/6] kselftest: factor out list manipulation to a helper Jakub Kicinski
2020-03-17 20:22 ` Kees Cook
2020-03-16 22:56 ` [PATCH v3 3/6] kselftest: create fixture objects Jakub Kicinski
2020-03-17 20:23 ` Kees Cook
2020-03-16 22:56 ` [PATCH v3 4/6] kselftest: run tests by fixture Jakub Kicinski
2020-03-17 20:25 ` Kees Cook [this message]
2020-03-16 22:56 ` [PATCH v3 5/6] kselftest: add fixture parameters Jakub Kicinski
2020-03-17 20:36 ` Kees Cook
2020-03-16 22:56 ` [PATCH v3 5/6] kselftest: add fixture variants Jakub Kicinski
2020-03-17 20:37 ` Kees Cook
2020-03-16 22:56 ` [PATCH v3 6/6] selftests: tls: run all tests for TLS 1.2 and TLS 1.3 Jakub Kicinski
2020-03-17 20:46 ` Kees Cook
2020-03-16 22:59 ` [PATCH v3 0/6] kselftest: add fixture parameters Jakub Kicinski
2020-03-17 20:47 ` Kees Cook
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=202003171324.E6E5FE7@keescook \
--to=keescook@chromium.org \
--cc=Tim.Bird@sony.com \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=wad@chromium.org \
/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;
as well as URLs for NNTP newsgroup(s).