Attaching the updated debdiff in case we do decide we want this (even in
the broken state)
** Patch added: "nftables_1.0.2-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1966017/+attachment/5572129/+files/nftables_1.0.2-1ubuntu2.debdiff
--
You received this bug not
Turns out I wasn't looking closely enough at the autopkgtest logs from
my local testing - I was trying to run the tests with the pre-built
binary packages and whilst it would indicate the internaltest-py.sh
tests were passing, they were actually completely failing without any
error indication:
aut
(If this were a build time testsuite, our log comparison process would
pick up changes. We could *maybe* do something akin to how we try to
detect new failing tests in openjdk in qrt's notes_testing/openjdk/
where we maybe compare our current adt runs of nftables against a prior
run, and look for d
So this looks okay, there are unfortunately a bunch of errors in the
tests with v1.0.2 against a 5.15 kernel because the 'egress' hook
support was only added in 5.16
(https://git.kernel.org/linus/42df6e1d221dddc0f2acf2be37e68d553ad65f96).
This results in the following output in a jammy VM:
96 te
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966017
Title:
enable upstream python testsuite in autopkgtests
To manage notifications about this bug go to:
https://bugs.launchp
** Patch added: "nftables_1.0.2-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1966017/+attachment/5572061/+files/nftables_1.0.2-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu