public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Benjamin Poirier <bpoirier@nvidia.com>
Cc: netdev@vger.kernel.org, Jay Vosburgh <j.vosburgh@gmail.com>,
	Andy Gospodarek <andy@greyhouse.net>,
	Shuah Khan <shuah@kernel.org>, Liang Li <liali@redhat.com>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net] selftests: bonding: Increase timeout to 1200s
Date: Thu, 18 Jan 2024 09:20:09 +0800	[thread overview]
Message-ID: <Zah8yeTwB6Xcc6nd@Laptop-X1> (raw)
In-Reply-To: <20240118001233.304759-1-bpoirier@nvidia.com>

On Wed, Jan 17, 2024 at 07:12:32PM -0500, Benjamin Poirier wrote:
> When tests are run by runner.sh, bond_options.sh gets killed before
> it can complete:
> 
> make -C tools/testing/selftests run_tests TARGETS="drivers/net/bonding"
> 	[...]
> 	# timeout set to 120
> 	# selftests: drivers/net/bonding: bond_options.sh
> 	# TEST: prio (active-backup miimon primary_reselect 0)                [ OK ]
> 	# TEST: prio (active-backup miimon primary_reselect 1)                [ OK ]
> 	# TEST: prio (active-backup miimon primary_reselect 2)                [ OK ]
> 	# TEST: prio (active-backup arp_ip_target primary_reselect 0)         [ OK ]
> 	# TEST: prio (active-backup arp_ip_target primary_reselect 1)         [ OK ]
> 	# TEST: prio (active-backup arp_ip_target primary_reselect 2)         [ OK ]
> 	#
> 	not ok 7 selftests: drivers/net/bonding: bond_options.sh # TIMEOUT 120 seconds
> 
> This test includes many sleep statements, at least some of which are
> related to timers in the operation of the bonding driver itself. Increase
> the test timeout to allow the test to complete.
> 
> I ran the test in slightly different VMs (including one without HW
> virtualization support) and got runtimes of 13m39.760s, 13m31.238s, and
> 13m2.956s. Use a ~1.5x "safety factor" and set the timeout to 1200s.
> 
> Fixes: 42a8d4aaea84 ("selftests: bonding: add bonding prio option test")
> Reported-by: Jakub Kicinski <kuba@kernel.org>
> Closes: https://lore.kernel.org/netdev/20240116104402.1203850a@kernel.org/#t
> Suggested-by: Jakub Kicinski <kuba@kernel.org>
> Signed-off-by: Benjamin Poirier <bpoirier@nvidia.com>
> ---
>  tools/testing/selftests/drivers/net/bonding/settings | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/drivers/net/bonding/settings b/tools/testing/selftests/drivers/net/bonding/settings
> index 6091b45d226b..79b65bdf05db 100644
> --- a/tools/testing/selftests/drivers/net/bonding/settings
> +++ b/tools/testing/selftests/drivers/net/bonding/settings
> @@ -1 +1 @@
> -timeout=120
> +timeout=1200
> -- 
> 2.43.0
> 

Thanks, I will check how to use busywait in bonding test.

Reviewed-by: Hangbin Liu <liuhangbin@gmail.com>

  reply	other threads:[~2024-01-18  1:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18  0:12 [PATCH net] selftests: bonding: Increase timeout to 1200s Benjamin Poirier
2024-01-18  1:20 ` Hangbin Liu [this message]
2024-01-19  2:40 ` 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=Zah8yeTwB6Xcc6nd@Laptop-X1 \
    --to=liuhangbin@gmail.com \
    --cc=andy@greyhouse.net \
    --cc=bpoirier@nvidia.com \
    --cc=j.vosburgh@gmail.com \
    --cc=kuba@kernel.org \
    --cc=liali@redhat.com \
    --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