From: Simon Horman <horms@kernel.org>
To: Hangbin Liu <liuhangbin@gmail.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>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] selftests: net: use slowwait to stabilize vrf_route_leaking test
Date: Wed, 18 Jun 2025 11:33:58 +0100 [thread overview]
Message-ID: <20250618103358.GB1699@horms.kernel.org> (raw)
In-Reply-To: <20250617105101.433718-2-liuhangbin@gmail.com>
On Tue, Jun 17, 2025 at 10:50:59AM +0000, Hangbin Liu wrote:
> The vrf_route_leaking test occasionally fails due to connectivity issues
> in our testing environment. A sample failure message shows that the ping
> check fails intermittently
>
> PING 2001:db8:16:2::2 (2001:db8:16:2::2) 56 data bytes
>
> --- 2001:db8:16:2::2 ping statistics ---
> 1 packets transmitted, 0 received, 100% packet loss, time 0ms
>
> TEST: Basic IPv6 connectivity [FAIL]
>
> This is likely due to insufficient wait time on slower machines. To address
> this, switch to using slowwait, which provides a longer and more reliable
> wait for setup completion.
>
> Before this change, the test failed 3 out of 10 times. After applying this
> fix, the test was run 30 times without any failure.
>
> Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-06-18 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 10:50 [PATCH net-next 0/2] selftests: net: use slowwait to make sure setup finished Hangbin Liu
2025-06-17 10:50 ` [PATCH net-next 1/2] selftests: net: use slowwait to stabilize vrf_route_leaking test Hangbin Liu
2025-06-18 10:33 ` Simon Horman [this message]
2025-06-17 10:51 ` [PATCH net-next 2/2] selftests: net: use slowwait to make sure IPv6 setup finished Hangbin Liu
2025-06-18 10:34 ` Simon Horman
2025-06-19 13:30 ` [PATCH net-next 0/2] selftests: net: use slowwait to make sure " 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=20250618103358.GB1699@horms.kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--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 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.