From: shuah <shuah@kernel.org>
To: Matthieu Baerts <matthieu.baerts@tessares.net>,
Kees Cook <keescook@chromium.org>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
mptcp <mptcp@lists.01.org>, shuah <shuah@kernel.org>
Subject: Re: [PATCH] selftests: settings: tests can be in subsubdirs
Date: Mon, 27 Jan 2020 10:16:57 -0700 [thread overview]
Message-ID: <bcce12e4-f122-10ae-dbc7-cc199d9716b6@kernel.org> (raw)
In-Reply-To: <602ab319-dcb9-4ac7-b2b8-f7b6072ddc03@tessares.net>
On 1/27/20 9:05 AM, Matthieu Baerts wrote:
> Hi Shuah, Kees,
>
> On 21/11/2019 19:52, Kees Cook wrote:
>> On Thu, Nov 21, 2019 at 05:32:42PM +0100, Matthieu Baerts wrote:
>>> Hi Shuah,
>>>
>>> First, thank you for maintaining the Kernel Selftest framework!
>>>
>>> On 22/10/2019 19:12, Matthieu Baerts wrote:
>>>> Commit 852c8cbf34d3 (selftests/kselftest/runner.sh: Add 45 second
>>>> timeout per test) adds support for a new per-test-directory "settings"
>>>> file. But this only works for tests not in a sub-subdirectories, e.g.
>>>>
>>>> - tools/testing/selftests/rtc (rtc) is OK,
>>>> - tools/testing/selftests/net/mptcp (net/mptcp) is not.
>>>>
>>>> We have to increase the timeout for net/mptcp tests which are not
>>>> upstreamed yet but this fix is valid for other tests if they need to
>>>> add
>>>> a "settings" file, see the full list with:
>>>>
>>>> tools/testing/selftests/*/*/**/Makefile
>>>>
>>>> Note that this patch changes the text header message printed at the end
>>>> of the execution but this text is modified only for the tests that are
>>>> in sub-subdirectories, e.g.
>>>>
>>>> ok 1 selftests: net/mptcp: mptcp_connect.sh
>>>>
>>>> Before we had:
>>>>
>>>> ok 1 selftests: mptcp: mptcp_connect.sh
>>>>
>>>> But showing the full target name is probably better, just in case a
>>>> subsubdir has the same name as another one in another subdirectory.
>>>>
>>>> Fixes: 852c8cbf34d3 (selftests/kselftest/runner.sh: Add 45 second
>>>> timeout per test)
>>>> Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
>>> Sorry to bother you again with this but by chance, did you have a
>>> look at
>>> the patch below? :)
>>>
>>> It doesn't only fix an issue with MPTCP, not in the kernel yet. But
>>> it also
>>> fixes the issue of taking the right "settings" file (if available)
>>> for any
>>> other tests in a sub-directory, e.g.:
>>>
>>> drivers/dma-buf
>>> filesystems/binderfs
>>> net/forwarding
>>> networking/timestamping
>>>
>>> But I guess all tests in powerpc/* dirs and others.
>>
>> Thanks for the ping! I missed this patch when you originally sent it.
>> Yes, this make sense to me:
>>
>> Reviewed-by: Kees Cook <keescook@chromium.org>
>
> Kees, Thank you for this review!
>
> Shuah, I am sorry to send you this new request. It is just to inform you
> that the first selftests for MPTCP are now in "net-next" repo, ready for
> the future Linux 5.6.
> We would then be very happy to see this patch here below for the
> kselftest framework accepted to avoid timeouts. Locally we apply this
> patch before running the selftests but we cannot ask everybody running
> MPTCP' selftests to do the same :)
>
>
I am sorry for the delay. My bad. Looks like I just missed it. I will
make sure it gets into 5.6-rc1
Thanks for your patience and ping.
thanks,
-- Shuah
next prev parent reply other threads:[~2020-01-27 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 17:12 [PATCH] selftests: settings: tests can be in subsubdirs Matthieu Baerts
2019-11-21 16:32 ` Matthieu Baerts
2019-11-21 18:52 ` Kees Cook
2020-01-27 16:05 ` Matthieu Baerts
2020-01-27 16:05 ` [MPTCP] " Matthieu Baerts
2020-01-27 17:16 ` shuah [this message]
2020-01-27 20:34 ` Matthieu Baerts
2020-01-27 20:34 ` [MPTCP] " Matthieu Baerts
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=bcce12e4-f122-10ae-dbc7-cc199d9716b6@kernel.org \
--to=shuah@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.