From: patchwork-bot+netdevbpf@kernel.org
To: Yunshui Jiang <jiangyunshui@kylinos.cn>
Cc: andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PATCH v2] tests: hsr: Increase timeout to 50 seconds
Date: Wed, 30 Oct 2024 23:50:30 +0000 [thread overview]
Message-ID: <173033223026.1495543.3228017262057371335.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241028082757.2945232-1-jiangyunshui@kylinos.cn>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 28 Oct 2024 16:27:56 +0800 you wrote:
> The HSR test, hsr_ping.sh, actually needs 7 min to run. Around 375s to
> be exact, and even more on a debug kernel or kernel with other network
> security limits. The timeout setting for the kselftest is currently 45
> seconds, which is way too short to integrate hsr tests to run_kselftest
> infrastructure. However, timeout of hundreds of seconds is quite a long
> time, especially in a CI/CD environment. It seems that we need
> accelerate the test and balance with timeout setting.
>
> [...]
Here is the summary with links:
- [v2] tests: hsr: Increase timeout to 50 seconds
https://git.kernel.org/netdev/net-next/c/365836e010a1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-10-30 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 8:02 [PATCH] tests: hsr: Increase timeout to 10 minutes Yunshui Jiang
2024-10-22 15:46 ` Simon Horman
2024-10-22 16:12 ` Andrew Lunn
2024-10-28 8:27 ` [PATCH v2] tests: hsr: Increase timeout to 50 seconds Yunshui Jiang
2024-10-30 23:50 ` patchwork-bot+netdevbpf [this message]
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=173033223026.1495543.3228017262057371335.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiangyunshui@kylinos.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.