From: Hangbin Liu <liuhangbin@gmail.com>
To: Wang Liang <wangliang74@huawei.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, yuehaibing@huawei.com,
zhangchangzhong@huawei.com
Subject: Re: [PATCH net-next] selftests: net: check jq command is supported
Date: Fri, 10 Oct 2025 10:02:13 +0000 [thread overview]
Message-ID: <aOjZpSSOVZg9INj6@fedora> (raw)
In-Reply-To: <20251010033043.140501-1-wangliang74@huawei.com>
On Fri, Oct 10, 2025 at 11:30:43AM +0800, Wang Liang wrote:
> The jq command is used in vlan_bridge_binding.sh, if it is not supported,
> the test will spam the following log.
>
> # ./vlan_bridge_binding.sh: line 51: jq: command not found
> # ./vlan_bridge_binding.sh: line 51: jq: command not found
> # ./vlan_bridge_binding.sh: line 51: jq: command not found
> # ./vlan_bridge_binding.sh: line 51: jq: command not found
> # ./vlan_bridge_binding.sh: line 51: jq: command not found
> # TEST: Test bridge_binding on->off when lower down [FAIL]
> # Got operstate of , expected 0
>
> The rtnetlink.sh has the same problem. It makes sense to check if jq is
> installed before running these tests. After this patch, the
> vlan_bridge_binding.sh skipped if jq is not supported:
>
> # timeout set to 3600
> # selftests: net: vlan_bridge_binding.sh
> # TEST: jq not installed [SKIP]
>
> Signed-off-by: Wang Liang <wangliang74@huawei.com>
> ---
> tools/testing/selftests/net/rtnetlink.sh | 2 ++
> tools/testing/selftests/net/vlan_bridge_binding.sh | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/tools/testing/selftests/net/rtnetlink.sh b/tools/testing/selftests/net/rtnetlink.sh
> index dbf77513f617..163a084d525d 100755
> --- a/tools/testing/selftests/net/rtnetlink.sh
> +++ b/tools/testing/selftests/net/rtnetlink.sh
> @@ -1466,6 +1466,8 @@ usage: ${0##*/} OPTS
> EOF
> }
>
> +require_command jq
> +
> #check for needed privileges
> if [ "$(id -u)" -ne 0 ];then
> end_test "SKIP: Need root privileges"
> diff --git a/tools/testing/selftests/net/vlan_bridge_binding.sh b/tools/testing/selftests/net/vlan_bridge_binding.sh
> index db481af9b6b3..e8c02c64e03a 100755
> --- a/tools/testing/selftests/net/vlan_bridge_binding.sh
> +++ b/tools/testing/selftests/net/vlan_bridge_binding.sh
> @@ -249,6 +249,8 @@ test_binding_toggle_off_when_upper_down()
> do_test_binding_off : "on->off when upper down"
> }
>
> +require_command jq
> +
> trap defer_scopes_cleanup EXIT
> setup_prepare
> tests_run
> --
> 2.34.1
>
Reviewed-by: Hangbin Liu <liuhangbin@gmail.com>
next prev parent reply other threads:[~2025-10-10 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 3:30 [PATCH net-next] selftests: net: check jq command is supported Wang Liang
2025-10-10 10:02 ` Hangbin Liu [this message]
2025-10-10 14:56 ` Paolo Abeni
2025-10-11 3:26 ` Wang Liang
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=aOjZpSSOVZg9INj6@fedora \
--to=liuhangbin@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=wangliang74@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=zhangchangzhong@huawei.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