From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v7 0/4] Introduce first exeter based test infrastructure
Date: Fri, 5 Sep 2025 11:35:53 +1000 [thread overview]
Message-ID: <aLo-eaXCJy3AEUZV@zatzit> (raw)
In-Reply-To: <20250905011433.41c0d242@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 2381 bytes --]
On Fri, Sep 05, 2025 at 01:14:33AM +0200, Stefano Brivio wrote:
> On Thu, 4 Sep 2025 12:50:00 +1000
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > Here's a new approach to building passt tests with exeter. This new
> > one no longer uses Avocado in the default case, although it would
> > still be possible to manually run the exeter based tests with Avocado.
> >
> > For now this only does simple tests, to show how the integration could
> > work. It adds some new trivial "smoke tests" and converts the linter
> > and build checks to exeter. More complex tests will require building
> > the tunbridge library we've discussed. A lot of the work for that
> > already exists in my earlier exeter test series, but it will need some
> > rework to split it into a separate component.
> >
> > v7:
> > * Use "exetool list" rather than "--list" directly to get test manifest.
> > * Update Makefiles to automatically update exeter sources as necessary.
> > * Update series cover letter removing some outdated information.
>
> I was about to apply this, but then realised that the usual build test
> links at https://passt.top/#ci disappeared, see also
> https://passt.top/builds/latest/web/ci.js.
Huh, that's weird.
> I didn't really investigate
> yet, we're missing something equivalent to the "test" directive.
We shouldn't be. exeter() calls status_test_{start,ok,fail} much like
test().
> If I
> recall correctly, that was working in v5, but I'm not sure why. I still
> need to look into this, unless you figure it out meanwhile.
Right, you said v5 worked. Hrm.... one of the main differences since
v5 is getting the descriptions, which *are* used as the parameter to
status_test_start. Could the descriptions be using some character we
weren't before and we're missing an escape somewhere? Not seeing an
obvious spot.
> Something minor I noticed is that indentation of some lines in
> run_selected() is broken now (spaces instead of tabs).
Drat, I thought I fixed my editor config for that. I've fixed it in
my branch, I'll hold of on another spin until we figure out what's
going on with the CI links.
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-09-05 6:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 2:50 [PATCH v7 0/4] Introduce first exeter based test infrastructure David Gibson
2025-09-04 2:50 ` [PATCH v7 1/4] test: Extend test scripts to allow running exeter tests David Gibson
2025-09-04 2:50 ` [PATCH v7 2/4] test: Run static checkers as " David Gibson
2025-09-04 2:50 ` [PATCH v7 3/4] test: Convert build tests to exeter David Gibson
2025-09-04 2:50 ` [PATCH v7 4/4] test: Allow exeter & podman tests to be parallel executed with BATS David Gibson
2025-09-04 23:14 ` [PATCH v7 0/4] Introduce first exeter based test infrastructure Stefano Brivio
2025-09-05 1:35 ` David Gibson [this message]
2025-09-05 6:42 ` David Gibson
2025-09-05 11:01 ` Stefano Brivio
2025-09-08 1:52 ` David Gibson
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=aLo-eaXCJy3AEUZV@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
/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).