Message ID | 20241022080223.718547-1-jiangyunshui@kylinos.cn (mailing list archive) |
---|---|
State | New |
Delegated to: | Netdev Maintainers |
Headers | show |
Series | tests: hsr: Increase timeout to 10 minutes | expand |
On Tue, Oct 22, 2024 at 04:02:23PM +0800, Yunshui Jiang wrote: > The time-consuming 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. So, HSR test needs an explicit setting. > And to leave us some slack, use 10 min as default timeout. > > Signed-off-by: Yunshui Jiang <jiangyunshui@kylinos.cn> Reviewed-by: Simon Horman <horms@kernel.org>
On Tue, Oct 22, 2024 at 04:02:23PM +0800, Yunshui Jiang wrote: > The time-consuming HSR test, hsr_ping.sh, actually needs 7 min to run. > Around 375s to be exact That is quite a long time, if it is being used in a CI/CD environment. If it possible to make the test faster? What takes all the time? Andrew
diff --git a/tools/testing/selftests/net/hsr/settings b/tools/testing/selftests/net/hsr/settings new file mode 100644 index 000000000000..a62d2fa1275c --- /dev/null +++ b/tools/testing/selftests/net/hsr/settings @@ -0,0 +1 @@ +timeout=600
The time-consuming 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. So, HSR test needs an explicit setting. And to leave us some slack, use 10 min as default timeout. Signed-off-by: Yunshui Jiang <jiangyunshui@kylinos.cn> --- tools/testing/selftests/net/hsr/settings | 1 + 1 file changed, 1 insertion(+) create mode 100644 tools/testing/selftests/net/hsr/settings