From: Simon Horman <horms@kernel.org>
To: Aaron Conole <aconole@redhat.com>
Cc: netdev@vger.kernel.org, dev@openvswitch.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
"Pravin B Shelar" <pshelar@ovn.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>,
"Adrián Moreno" <amorenoz@redhat.com>
Subject: Re: [PATCH net-next 1/3] selftests: openvswitch: Bump timeout to 15 minutes.
Date: Wed, 3 Jul 2024 17:55:15 +0100 [thread overview]
Message-ID: <20240703165515.GS598357@kernel.org> (raw)
In-Reply-To: <20240702132830.213384-2-aconole@redhat.com>
On Tue, Jul 02, 2024 at 09:28:28AM -0400, Aaron Conole wrote:
> We found that since some tests rely on the TCP SYN timeouts to cause flow
> misses, the default test suite timeout of 45 seconds is quick to be
> exceeded. Bump the timeout to 15 minutes.
>
> Signed-off-by: Aaron Conole <aconole@redhat.com>
Reviewed-by: Simon Horman <horms@kernel.org>
Tested-by: Simon Horman <horms@kernel.org>
FWIIW, locally I had been using a timeout of 720s.
So 900 seems entirely reasonable to me.
next prev parent reply other threads:[~2024-07-03 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 13:28 [PATCH net-next 0/3] selftests: openvswitch: Address some flakes in the CI environment Aaron Conole
2024-07-02 13:28 ` [PATCH net-next 1/3] selftests: openvswitch: Bump timeout to 15 minutes Aaron Conole
2024-07-03 16:55 ` Simon Horman [this message]
2024-07-02 13:28 ` [PATCH net-next 2/3] selftests: openvswitch: Attempt to autoload module Aaron Conole
2024-07-03 16:55 ` Simon Horman
2024-07-02 13:28 ` [PATCH net-next 3/3] selftests: openvswitch: Be more verbose with selftest debugging Aaron Conole
2024-07-03 16:55 ` Simon Horman
2024-07-04 2:40 ` [PATCH net-next 0/3] selftests: openvswitch: Address some flakes in the CI environment patchwork-bot+netdevbpf
2024-07-05 13:28 ` Jakub Kicinski
2024-07-05 13:49 ` Aaron Conole
2024-07-05 13:53 ` Jakub Kicinski
2024-07-05 14:01 ` Adrián Moreno
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=20240703165515.GS598357@kernel.org \
--to=horms@kernel.org \
--cc=aconole@redhat.com \
--cc=amorenoz@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.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 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.