Bug#1032968: unblock: passt/0.0~git20230309.7c7625d-1
On Thu, 16 Mar 2023 16:22:33 +0100
Paul Gevers <elbrus@debian.org> wrote:
> Hi Stefano,
>
> On 14-03-2023 22:44, Stefano Brivio wrote:
> > - full slirp4netns(1) compatibility not granted
>
> I've never heard of this before, what does that mean for the user?
pasta(1) is supposed to provide a drop-in replacement for
slirp4netns(1): you create a network namespace, as a regular user, and
it can give that namespace network connectivity without creating any
interface outside it.
The main distinction is that it's written with performance, IPv6, and
security in mind, but functionally it's supposed to be a superset of it.
It has other functionalities (such as full IPv6 support), so it's not
useless otherwise, but it's probably unexpected for users (and I see
it as a source of potential bugs) that they can't set an outbound
address as they could do it on slirp4netns.
> > [ Tests ]
> > I ran the upstream test suite against the packaged version on a
> > Debian testing (Bookworm) x86_64 system.
>
> If you can do this manually, you can probably also do it automatically.
> If you turn this into an autopkgtest [1] your package could migrate
> without our intervention (providing that it passes on all architectures
> where the binary builds and that it tests a substantial part of the
> as-installed binaries).
Salsa seems to be inaccessible at the moment (and I can't fetch that
link from archive.org), but yes, I started reading about it just after
I realised the migration was blocked, so I know a bit already.
The current problem with the upstream test suite is that it takes a
long time to complete, and has a lot of dependencies, including things
that are not packaged in Debian (e.g. https://github.com/google/neper/).
But most of those dependencies (and time) are only needed for
performance tests, and we're working to refactor the test framework to
make it reasonably modular. It's not exactly trivial as we spawn virtual
machines and there are context dependencies between test cases, so it
will probably take a while. Just to give an idea, screen capture of
latest run:
https://passt.top/#continuous-integration
Once that is done, it should be trivial (from what I remember of the
document you linked) to create autopkgtests for it.
We also have optional tests (which I run from time to time) to check
build and basic functionality on several distributions, including a few
flavours of Debian:
https://passt.top/passt/tree/test/distro/debian
but that makes little sense now that it's packaged (and that we'll be
able to have distribution tests... in distributions, eventually).
--
Stefano
Reply to: