On 2/14/26 8:59 AM, Frode Nordahl wrote:
External email: Use caution opening links or attachments
On 2/13/26 22:37, Ihar Hrachyshka via dev wrote:
This reduces the number of skipped tests from 181 to 39.
Signed-off-by: Ihar Hrachyshka <[email protected]>
Hello, Ihar,
Thank you for the patch.
Hi Frode, thanks for the quick reply!
---
debian/control | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index d99b483ac..4491578c8 100644
--- a/debian/control
+++ b/debian/control
@@ -19,7 +19,16 @@ Build-Depends: graphviz,
python3-twisted,
python3-zope.interface,
libunbound-dev,
- libunwind-dev
+ libunwind-dev,
+ util-linux,
+ python3-scapy,
+ tcpdump,
+ netcat-openbsd,
+ xxd,
+ iproute2,
+ arping,
+ ethtool,
+ nftables
I would rather not have build dependencies added here that are not
strictly required for compilation of the software itself.
Every dependency is a potential liability and added maintenance burden.
The quest to run more unit tests is a noble one and I'd advice you to do
this separately instead.
We do this already for the system testsuite [0][1], and there is nothing
stopping us from expanding this to the unit testsuite.
Yes, this seems preferable since tests may indeed be flaky.
Though if we believe that running integration tests shouldn't be part of
the main package build, then why do we run most of these tests today
(and skip only those that happen to depend on a non-existing tool)?
Should *all* tests move elsewhere? (Should nocheck become the default?)
---
Curious: you shared links to packaging files that are outside of OVN
tree. I assume they are part of official Debian/Ubuntu packaging, which
is different from the in-tree packaging. What is the relationship
between these distinct packages (in-tree vs. debian/ubuntu)? Should
these be reconciled?
For context: I'm trying to see if I can use the *in-tree* debian/ to
build custom packages for our downstream build pipeline for OVS and OVN.
I assume in-tree is a viable path, but I am not a Debian packaging
expert, so looking for best practices.
WDYT?
0:
https://salsa.debian.org/openstack-team/third-party/ovn/-/blob/debian/sid/debian/tests/control?ref_type=heads
1:
https://salsa.debian.org/openstack-team/third-party/ovn/-/blob/debian/sid/debian/tests/run-tests.sh?ref_type=heads
--
Frode Nordahl
Standards-Version: 3.9.3
Homepage: http://www.ovn.org/
--
2.52.0
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
