From: Daniel Latypov <dlatypov@google.com>
To: Marco Elver <elver@google.com>
Cc: kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
David Gow <davidgow@google.com>,
Brendan Higgins <brendanhiggins@google.com>
Subject: Re: [PATCH -kselftest/kunit] kcsan: test: use new suite_{init,exit} support
Date: Wed, 4 May 2022 11:13:46 -0500 [thread overview]
Message-ID: <CAGS_qxq504dLbF_MWaJwNqLobjPAdZ2HOBFAiivpDE_WDYN+zA@mail.gmail.com> (raw)
In-Reply-To: <20220504070941.2798233-1-elver@google.com>
On Wed, May 4, 2022 at 2:09 AM Marco Elver <elver@google.com> wrote:
>
> Use the newly added suite_{init,exit} support for suite-wide init and
> cleanup. This avoids the unsupported method by which the test used to do
> suite-wide init and cleanup (avoiding issues such as missing TAP
> headers, and possible future conflicts).
>
> Signed-off-by: Marco Elver <elver@google.com>
Reviewed-by: Daniel Latypov <dlatypov@google.com>
Adding '-smp 16' and CONFIG_KCSAN_REPORT_ONCE_IN_MS=100 as you
suggested below, I was able to get it running under kunit.py with the
following results:
Testing complete. Passed: 168, Failed: 0, Crashed: 0, Skipped: 1, Errors: 0
Elapsed time: 92.642s total, 0.003s configuring, 4.592s building,
88.009s running
Nice!
next prev parent reply other threads:[~2022-05-04 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 7:09 [PATCH -kselftest/kunit] kcsan: test: use new suite_{init,exit} support Marco Elver
2022-05-04 13:43 ` David Gow
2022-05-04 13:47 ` Marco Elver
2022-05-04 13:54 ` David Gow
2022-05-04 13:58 ` Marco Elver
2022-05-04 15:56 ` Daniel Latypov
2022-05-04 16:13 ` Daniel Latypov [this message]
2022-05-12 19:17 ` Brendan Higgins
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=CAGS_qxq504dLbF_MWaJwNqLobjPAdZ2HOBFAiivpDE_WDYN+zA@mail.gmail.com \
--to=dlatypov@google.com \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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).