From: Shuah Khan <shuah@kernel.org>
To: Ido Schimmel <idosch@idosch.org>,
Anders Roxell <anders.roxell@linaro.org>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] selftests: net: move fragment forwarding/config up a level
Date: Tue, 21 Aug 2018 13:41:54 -0600 [thread overview]
Message-ID: <fa188bdd-2f4c-66fc-a803-5d53425c3daf@kernel.org> (raw)
In-Reply-To: <20180821185625.GB27078@splinter>
On 08/21/2018 12:56 PM, Ido Schimmel wrote:
> On Tue, Aug 21, 2018 at 06:12:12PM +0200, Anders Roxell wrote:
>> 'make kselftest-merge' assumes that the config files for the tests are
>> located under the 'main' tet dir, like tools/testing/selftests/net/ and
>> not in a subdir to net.
>
> The tests under tools/testing/selftests/net/forwarding/ aren't executed
> as part of the Makefile. The config file is there mainly so that people
> will know which config options they need in order to run the tests.
>
> The tests can be added to the Makefile, but some of them take a few
> minutes to complete which is probably against "Don't take too long;"
> mentioned in Documentation/dev-tools/kselftest.rst.
>
I don't see any reason why these shouldn't be added. With the number of
tests that get run by default, time has gone up. The goal is to run more
tests not less. There are some stress/destructive tests that continue to
be left out of the Makefile.
thanks,
-- Shuah
next prev parent reply other threads:[~2018-08-21 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 16:12 [PATCH] selftests: net: move fragment forwarding/config up a level Anders Roxell
2018-08-21 18:56 ` Ido Schimmel
2018-08-21 19:41 ` Shuah Khan [this message]
2018-08-22 6:45 ` Ido Schimmel
2018-08-23 17:09 ` Shuah Khan
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=fa188bdd-2f4c-66fc-a803-5d53425c3daf@kernel.org \
--to=shuah@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.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).