From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Jon Maloy <jmaloy@redhat.com>, passt-dev@passt.top
Subject: Re: "test in a box"
Date: Fri, 15 Mar 2024 09:41:55 +0100 [thread overview]
Message-ID: <20240315094155.2397ab6f@elisabeth> (raw)
In-Reply-To: <ZfPDmQxRgrLMGr5X@zatzit>
On Fri, 15 Mar 2024 13:42:17 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> Hi Jon (and others),
>
> Are you still having trouble getting the passt tests to work? I
> mentioned at some point in the past that I had an experimental "test
> in a box" script which set up some namespaces to run the tests
> independently of the host's networking setup. I just rebased that
> onto the current tree and discovered that it worked better than I
> recalled. I was able to run the full test suite except for the
> performance tests - I didn't try those, so I don't know if they work.
>
> I pushed the rebased version, along with some other local patches I
> tend to use while developing at:
> https://gitlab.com/dgibson/passt/-/tree/testbase?ref_type=heads
>
> To use:
>
> 1) The test "assets" must be built and up to date, first, so in
> passt/tests run:
> $ make
> 2) In passt/tests run
> $ ./testinabox.sh
>
> Hope that's useful to someone.
Actually, it would be generally useful to have this "on" in the tests
by default, either as a wrapper or integrated in a different way.
I maintain Debian and Fedora packages but I can only run manual tests
on them, and other packagers have the same kind of issue. In particular,
the lack of an autopkgtest possibility for Debian turns a release soft
freeze into a hard freeze:
https://release.debian.org/bookworm/freeze_policy.html#hard
I know, the plan is to eventually replace this test suite altogether,
but your script is small and rather inviting...
--
Stefano
prev parent reply other threads:[~2024-03-15 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 3:42 "test in a box" David Gibson
2024-03-15 4:37 ` David Gibson
2024-03-15 8:41 ` Stefano Brivio [this message]
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=20240315094155.2397ab6f@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=jmaloy@redhat.com \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).