From: Petr Machata <petrm@nvidia.com>
To: Pablo Martin Medrano <pablmart@redhat.com>
Cc: <netdev@vger.kernel.org>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH net v2] selftests/net: big_tcp: return xfail on slow machines
Date: Tue, 25 Feb 2025 14:01:10 +0100 [thread overview]
Message-ID: <87zfiagojj.fsf@nvidia.com> (raw)
In-Reply-To: <23340252eb7bbc1547f5e873be7804adbd7ad092.1739983848.git.pablmart@redhat.com>
Pablo Martin Medrano <pablmart@redhat.com> writes:
> diff --git a/tools/testing/selftests/net/big_tcp.sh b/tools/testing/selftests/net/big_tcp.sh
> index 2db9d15cd45f..dc2ecfd58961 100755
> --- a/tools/testing/selftests/net/big_tcp.sh
> +++ b/tools/testing/selftests/net/big_tcp.sh
> @@ -21,8 +21,7 @@ CLIENT_GW6="2001:db8:1::2"
> MAX_SIZE=128000
> CHK_SIZE=65535
>
> -# Kselftest framework requirement - SKIP code is 4.
> -ksft_skip=4
> +source lib.sh
>
> setup() {
> ip netns add $CLIENT_NS
> @@ -143,21 +142,20 @@ do_test() {
Just a small comment.
In general it is a good hygiene to have a RET=0 for each log_test(). A
test that neglects to set it will get a spurious failure if it comes
after a failing test. Arguably log_test() should do this automatically,
but currently it does not.
Due to all the &&'s peppered down there, do_test() only gets called at
most once, so it's OK in this case.
> start_counter link3 $SERVER_NS
> do_netperf $CLIENT_NS
>
> - if check_counter link1 $ROUTER_NS; then
> - check_counter link3 $SERVER_NS || ret="FAIL_on_link3"
> - else
> - ret="FAIL_on_link1"
> - fi
> + check_counter link1 $ROUTER_NS
> + check_err $? "fail on link1"
> + check_counter link3 $SERVER_NS
> + check_err $? "fail on link3"
>
> stop_counter link1 $ROUTER_NS
> stop_counter link3 $SERVER_NS
> - printf "%-9s %-8s %-8s %-8s: [%s]\n" \
> - $cli_tso $gw_gro $gw_tso $ser_gro $ret
> + log_test "$(printf "%-9s %-8s %-8s %-8s" \
> + $cli_tso $gw_gro $gw_tso $ser_gro)"
> test $ret = "PASS"
> }
>
> testup() {
> - echo "CLI GSO | GW GRO | GW GSO | SER GRO" && \
> + echo " CLI GSO | GW GRO | GW GSO | SER GRO" && \
> do_test "on" "on" "on" "on" && \
> do_test "on" "off" "on" "off" && \
> do_test "off" "on" "on" "on" && \
> @@ -176,7 +174,8 @@ if ! ip link help 2>&1 | grep gso_ipv4_max_size &> /dev/null; then
> fi
>
> trap cleanup EXIT
> +xfail_on_slow
> setup && echo "Testing for BIG TCP:" && \
> NF=4 testup && echo "***v4 Tests Done***" && \
> NF=6 testup && echo "***v6 Tests Done***"
> -exit $?
> +exit $EXIT_STATUS
next prev parent reply other threads:[~2025-02-25 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 17:07 [PATCH net v2] selftests/net: big_tcp: return xfail on slow machines Pablo Martin Medrano
2025-02-24 13:44 ` Simon Horman
2025-02-24 17:34 ` Pablo Martin Medrano
2025-02-25 10:24 ` Simon Horman
2025-02-25 12:56 ` Petr Machata
2025-02-26 17:32 ` Pablo Martin Medrano
2025-02-25 13:01 ` Petr Machata [this message]
2025-02-26 18:53 ` Pablo Martin Medrano
2025-02-27 10:42 ` Petr Machata
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=87zfiagojj.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablmart@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).