From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Akihiko Odaki" <akihiko.odaki@daynix.com>,
"Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Cleber Rosa" <crosa@redhat.com>
Subject: Re: Avocado 88.1 vs Python 3.12
Date: Thu, 11 Jul 2024 13:30:26 +0100 [thread overview]
Message-ID: <Zo_QYmbLBFsPv8Ia@redhat.com> (raw)
In-Reply-To: <4aa7d5cd-259b-4b63-9ce2-b73c9027848f@redhat.com>
On Thu, Jul 11, 2024 at 02:01:25PM +0200, Thomas Huth wrote:
> On 10/07/2024 01.45, Richard Henderson wrote:
> > On 7/9/24 09:26, Philippe Mathieu-Daudé wrote:
> > > On 9/7/24 17:41, Richard Henderson wrote:
> > > > Hi guys,
> > > >
> > > > I have reinstalled my development box to ubuntu 24 (because the
> > > > Rust support is better than my previous install; ho hum). I
> > > > thought I had tested everything in a VM before committing, but I
> > > > missed out on Avocado:
> > > >
> > > > > AVOCADO Downloading avocado tests VM image for aarch64
> > > > > Failed to load plugin from module "avocado.plugins.list":
> > > > > ModuleNotFoundError("No module named 'imp'") :
> > >
> > >
> > > > If I understand things correctly, the python "imp" package was
> > > > deprecated, and has been removed before v3.12. This is fixed in
> > > > upstream avocado as of v93. But we have a hard stop in
> > > > pythondeps.toml at v92.
> > > >
> > > > Remind me what the blocker is to upgrading?
> > >
> > > IIRC we're waiting for v2 of:
> > > https://lore.kernel.org/qemu-devel/20231208190911.102879-1-crosa@redhat.com/
> >
> > Yes indeed. There are two minor conflicts in rebasing this branch, but
> > otherwise it works. Cleber, do you have time to pick this up again?
>
> As an alternative, if nobody has time to work on that Avocado update, we
> could maybe also try to integrate the python-based tests directly with the
> meson test runner. A prototype can be found here:
>
> https://lore.kernel.org/qemu-devel/20240711115546.40859-1-thuth@redhat.com/
Ooh, that looks remarkably straightford. I'd love to see use using pytest as
the test harness, even if we keep using avocado framework in some of the
test case impls.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2024-07-11 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 15:41 Avocado 88.1 vs Python 3.12 Richard Henderson
2024-07-09 16:26 ` Philippe Mathieu-Daudé
2024-07-09 23:45 ` Richard Henderson
2024-07-11 12:01 ` Thomas Huth
2024-07-11 12:30 ` Daniel P. Berrangé [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=Zo_QYmbLBFsPv8Ia@redhat.com \
--to=berrange@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=crosa@redhat.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=wainersm@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.
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 NNTP newsgroup(s).