From: Shuah Khan <skhan@linuxfoundation.org>
To: Abhinav <singhabhinav9051571833@gmail.com>, shuah@kernel.org
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] Added missing TARGETS in kselftest top level Makefile
Date: Mon, 2 Oct 2023 08:34:16 -0600 [thread overview]
Message-ID: <087c5c0d-6a20-e58b-7735-d764c4de69af@linuxfoundation.org> (raw)
In-Reply-To: <20231002114635.1567809-1-singhabhinav9051571833@gmail.com>
On 10/2/23 05:46, Abhinav wrote:
> Some tests like dma, ia64, etc. were not present in top level of
> selftest Makefile, so when someone ran 'make run_tests' they would miss
> these tests. This patches adds those left out tests.
>
> Signed-off-by: Abhinav <singhabhinav9051571833@gmail.com>
> ---
>
> I removed sched, safesetid and filelock from the Makefile, because these
> tests were actually triggered when we run 'make run_tests' even though it
> has not been mentioned explicitly inside top level Makefile of selftest.
>
> tools/testing/selftests/Makefile | 7 +++++++
> 1 file changed, 7 insertions(+)
>
There are good reasons to leave out tests from the kselftest default
run.
1. test requires specific hardware or driver or system configuration
which includes kernel configuration options.
e.g: media_tests, dma
2. It is a benchmark and/or destructive test that doesn't fit into
default run category: watchdog, kmod
3. test Makefile doesn't support kselftest framework
Any patch adding a test left out of default run to the default
run has to explain the reasons why it is a good idea to add it
and more importantly showing that this doesn't impact the default
run with report from the test run "make kselftest"
Sorry. I am not going to take this patch.
thanks,
-- Shuah
prev parent reply other threads:[~2023-10-02 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 19:41 [PATCH] Added missing TARGETS in kselftest top level Makefile Abhinav
2023-10-01 6:07 ` Greg KH
2023-10-02 7:27 ` [PATCH v2] " Abhinav
2023-10-02 8:58 ` Greg KH
2023-10-02 11:46 ` Abhinav
2023-10-02 14:34 ` Shuah Khan [this message]
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=087c5c0d-6a20-e58b-7735-d764c4de69af@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=singhabhinav9051571833@gmail.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