From: Paolo Abeni <pabeni@redhat.com>
To: Taehee Yoo <ap420073@gmail.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
shuah@kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net] selftests: net: avoid waiting for server in amt.sh forever when it fails.
Date: Thu, 09 May 2024 11:36:27 +0200 [thread overview]
Message-ID: <d5016925e415c422c37f7ac1c5374a06bbdc2126.camel@redhat.com> (raw)
In-Reply-To: <20240508040643.229383-1-ap420073@gmail.com>
On Wed, 2024-05-08 at 04:06 +0000, Taehee Yoo wrote:
> @@ -210,40 +217,52 @@ check_features()
>
> test_ipv4_forward()
> {
> - RESULT4=$(ip netns exec "${LISTENER}" nc -w 1 -l -u 239.0.0.1 4000)
> + echo "" > $RESULT
> + bash -c "$(ip netns exec "${LISTENER}" \
> + timeout 10s > $RESULT)"
> + RESULT4=$(< $RESULT)
if you instead do:
RESULT4=$(timeout 10s ip netns exec \
"${LISTENER}" nc -w 1 -l -u 239.0.0.1 4000)
You can avoid the additional tmp file (RESULT)
> if [ "$RESULT4" == "172.17.0.2" ]; then
> printf "TEST: %-60s [ OK ]\n" "IPv4 amt multicast forwarding"
> - exit 0
> else
> printf "TEST: %-60s [FAIL]\n" "IPv4 amt multicast forwarding"
> - exit 1
> fi
> +
> }
[...]
> @@ -259,19 +278,17 @@ setup_iptables
> setup_mcast_routing
> test_remote_ip
> test_ipv4_forward &
> -pid=$!
> -send_mcast4
> -wait $pid || err=$?
> -if [ $err -eq 1 ]; then
> - ERR=1
> -fi
> +spid=$!
> +send_mcast4 &
> +cpid=$!
> +wait $spid
It looks like you don't capture anymore the return code from
test_ipv4_forward, why?
That will foul the test runner infra to think that this test is always
successful.
Paolo
next prev parent reply other threads:[~2024-05-09 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 4:06 [PATCH net] selftests: net: avoid waiting for server in amt.sh forever when it fails Taehee Yoo
2024-05-09 8:38 ` Simon Horman
2024-05-10 4:57 ` Taehee Yoo
2024-05-09 9:36 ` Paolo Abeni [this message]
2024-05-10 5:05 ` Taehee Yoo
2024-05-09 16:22 ` Jakub Kicinski
2024-05-10 5:17 ` Taehee Yoo
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=d5016925e415c422c37f7ac1c5374a06bbdc2126.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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