From: Brendan Higgins <brendanhiggins@google.com>
To: David Gow <davidgow@google.com>
Cc: Alan Maguire <alan.maguire@oracle.com>,
Marco Elver <elver@google.com>,
Daniel Latypov <dlatypov@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
KUnit Development <kunit-dev@googlegroups.com>,
kasan-dev <kasan-dev@googlegroups.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrey Konovalov <andreyknvl@gmail.com>
Subject: Re: [PATCH v3 4/4] kasan: test: make use of kunit_skip()
Date: Tue, 8 Jun 2021 14:23:26 -0700 [thread overview]
Message-ID: <CAFd5g441kq9KsmeFr_OgbexShN-rJRzrh97kxxYRmC7Yvt+g-w@mail.gmail.com> (raw)
In-Reply-To: <20210608065128.610640-1-davidgow@google.com>
On Mon, Jun 7, 2021 at 11:51 PM David Gow <davidgow@google.com> wrote:
>
> From: Marco Elver <elver@google.com>
>
> Make use of the recently added kunit_skip() to skip tests, as it permits
> TAP parsers to recognize if a test was deliberately skipped.
>
> Signed-off-by: Marco Elver <elver@google.com>
> Signed-off-by: David Gow <davidgow@google.com>
> Reviewed-by: Daniel Latypov <dlatypov@google.com>
> Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
next prev parent reply other threads:[~2021-06-08 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 6:48 [PATCH v3 1/4] kunit: Support skipped tests David Gow
2021-06-08 6:50 ` [PATCH v3 2/4] kunit: tool: Support skipped tests in kunit_tool David Gow
2021-06-08 21:21 ` Brendan Higgins
2021-06-08 6:51 ` [PATCH v3 3/4] kunit: test: Add example tests which are always skipped David Gow
2021-06-08 21:22 ` Brendan Higgins
2021-06-08 6:51 ` [PATCH v3 4/4] kasan: test: make use of kunit_skip() David Gow
2021-06-08 21:23 ` Brendan Higgins [this message]
2021-06-08 9:51 ` [PATCH v3 1/4] kunit: Support skipped tests kernel test robot
2021-06-08 11:01 ` kernel test robot
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=CAFd5g441kq9KsmeFr_OgbexShN-rJRzrh97kxxYRmC7Yvt+g-w@mail.gmail.com \
--to=brendanhiggins@google.com \
--cc=alan.maguire@oracle.com \
--cc=andreyknvl@gmail.com \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@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).