From: Jakub Kicinski <kuba@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>,
"Paolo Abeni" <pabeni@redhat.com>,
"Shuah Khan" <shuah@kernel.org>,
"Stefano Brivio" <sbrivio@redhat.com>,
"Adrián Moreno" <amorenoz@redhat.com>,
"Simon Horman" <horms@kernel.org>
Subject: Re: [PATCH net-next v3 0/7] selftests: net: Switch pmtu.sh to use the internal ovs script.
Date: Fri, 28 Jun 2024 08:15:26 -0700 [thread overview]
Message-ID: <20240628081526.66a6b5c6@kernel.org> (raw)
In-Reply-To: <20240625172245.233874-1-aconole@redhat.com>
On Tue, 25 Jun 2024 13:22:38 -0400 Aaron Conole wrote:
> Currently, if a user wants to run pmtu.sh and cover all the provided test
> cases, they need to install the Open vSwitch userspace utilities. This
> dependency is difficult for users as well as CI environments, because the
> userspace build and setup may require lots of support and devel packages
> to be installed, system setup to be correct, and things like permissions
> and selinux policies to be properly configured.
Hi Aaron!
I merged this yesterday (with slight alphabetical reshuffling of
the config options). The pmtu.sh test is solid now, which is great!
I also added the OvS tests themselves, and those are not passing, yet:
https://netdev.bots.linux.dev/contest.html?test=openvswitch-sh
Could you take a look and LMK if these are likely env issues or
something bad in the test itself?
next prev parent reply other threads:[~2024-06-28 15:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 17:22 [PATCH net-next v3 0/7] selftests: net: Switch pmtu.sh to use the internal ovs script Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 1/7] selftests: openvswitch: Support explicit tunnel port creation Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 2/7] selftests: openvswitch: Refactor actions parsing Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 3/7] selftests: openvswitch: Add set() and set_masked() support Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 4/7] selftests: openvswitch: Add support for tunnel() key Aaron Conole
2024-06-26 16:55 ` Simon Horman
2024-06-25 17:22 ` [PATCH net-next v3 5/7] selftests: openvswitch: Support implicit ipv6 arguments Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 6/7] selftests: net: Use the provided dpctl rather than the vswitchd for tests Aaron Conole
2024-06-26 16:54 ` Simon Horman
2024-06-27 13:46 ` Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 7/7] selftests: net: add config for openvswitch Aaron Conole
2024-06-27 23:00 ` [PATCH net-next v3 0/7] selftests: net: Switch pmtu.sh to use the internal ovs script patchwork-bot+netdevbpf
2024-06-28 15:15 ` Jakub Kicinski [this message]
2024-06-28 18:04 ` Aaron Conole
2024-06-28 23:37 ` Jakub Kicinski
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=20240628081526.66a6b5c6@kernel.org \
--to=kuba@kernel.org \
--cc=aconole@redhat.com \
--cc=amorenoz@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=horms@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=sbrivio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).