From: Jakub Kicinski <kuba@kernel.org>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net 0/2] selftests: net: add missing tests to Makefile
Date: Wed, 18 May 2022 08:25:48 -0700 [thread overview]
Message-ID: <20220518082548.24d63e25@kernel.org> (raw)
In-Reply-To: <YoSLx329qjT4Vrev@Laptop-X1>
On Wed, 18 May 2022 14:01:43 +0800 Hangbin Liu wrote:
> > > +files=$(git show --name-status --oneline | grep -P '^A\ttools/testing/selftests/net/' | grep '\.sh$' | sed 's@A\ttools/testing/selftests/net/@@')
FWIW this will list just the names of bash scripts with no decoration:
git show --pretty="" --name-only -- tools/testing/selftests/*.sh
And we can get the names of the files with basename:
for f in $(git show --pretty="" --name-only); do basename $f; done
> > > +for file in $files; do
> > > + if echo $file | grep forwarding; then
> > > + file=$(echo $file | sed 's/forwarding\///')
> > > + if ! grep -P "[\t| ]$file" tools/testing/selftests/net/forwarding/Makefile;then
> > > + echo "new test $file not in selftests/net/forwarding/Makefile" >&$DESC_FD
> > > + rc=1
> > > + fi
> > > + else
> > > + if ! grep -P "[\t| ]$file" tools/testing/selftests/net/Makefile;then
> > > + echo "new test $file not in selftests/net/Makefile" >&$DESC_FD
> > > + rc=1
> > > + fi
> >
> > Does it matter which exact selftest makefile the changes are?
>
> I only checked the tools/testing/selftests/net/Makefile and
> tools/testing/selftests/net/forwarding/Makefile at present.
> Maybe mptcp should also added?
Right, mptcp is one example, then we also have
tools/testing/selftests/drivers/net/
There may be new directories added, then we'd need to keep updating
the test.
> > Maybe as a first stab we should just check if there are changes
> > to anything in tools/testing/selftests/.*/Makefile?
>
> In my checking only shell scripts are checked, as most net net/forwarding tests
> using shell script for testing. But other sub-component may use c binary or
> python for testing. So I think there is no need to check all
> tools/testing/selftests/.*/Makefile. WDYT?
Not sure I understand, let me explain what I meant in more detail.
I think we should make it generic. For example check the Makefile
in the same location as the script:
grep $(basename $f) $(dirname $f)/Makefile
And maybe just to be safe one directory level down?
grep $(basename $f) $(dirname $(dirname $f))/Makefile
Instead of hardcoding the expected paths.
next prev parent reply other threads:[~2022-05-18 15:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 4:45 [PATCH net 0/2] selftests: net: add missing tests to Makefile Hangbin Liu
2022-04-28 4:45 ` [PATCH net 1/2] selftests/net: " Hangbin Liu
2022-04-28 4:45 ` [PATCH net 2/2] selftests/net/forwarding: " Hangbin Liu
2022-04-30 0:56 ` [PATCH net 0/2] selftests: net: " Jakub Kicinski
2022-05-04 3:00 ` Hangbin Liu
2022-05-17 6:23 ` Hangbin Liu
2022-05-17 19:45 ` Jakub Kicinski
2022-05-18 6:01 ` Hangbin Liu
2022-05-18 15:25 ` Jakub Kicinski [this message]
2022-05-19 3:13 ` Hangbin Liu
2022-04-30 1:00 ` patchwork-bot+netdevbpf
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=20220518082548.24d63e25@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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).