From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"John Snow" <jsnow@redhat.com>
Subject: Re: [RFC 0/2] python: integrate linter tests natively with meson
Date: Mon, 14 Apr 2025 17:14:50 +0100 [thread overview]
Message-ID: <Z_00erYFFJ0EPMFa@redhat.com> (raw)
In-Reply-To: <20250224191152.2123003-1-berrange@redhat.com>
Ping: would like to hear John's thoughts on this series.
We're likely to eliminate usage of avocado for functional testing
in this dev cycle. That leaves python testing as the main outstanding
bit of QEMU that is not natively using meson's test integration and
also still pulling in avocado as a dependency.
On Mon, Feb 24, 2025 at 07:11:50PM +0000, Daniel P. Berrangé wrote:
> It seems everytime I post some new patches which touch python code I
> end up forgetting to run the extra non-default 'make check' target from
> the python/ subdir.
>
> IMHO, if we're going to pick up on linter failures in review feedback
> (which is a reasonable thing to want to do), then we should be running
> these linters by default in 'make check'.
>
> This RFC is demonstrating a possible strategy to achieve that, by making
> the python tests use meson in the same way as everything else, instead
> of being stuck in the old 'make' world. In keeping with our work to
> remove use of avocado for functional testing, this also removes avocado
> for python linters since IMHO it adds no notable value over what meson
> provides already.
>
> See last patch for the interesting stuff, and the various caveats about
> this initial PoC.
>
> Being a PoC this is minimally tested beyond 'make check' on my local
> machine.
>
> Daniel P. Berrangé (2):
> python: be more selective in hiding mypy subclassing warning
> python: integrate linter tests natively with meson
>
> meson.build | 1 +
> python/meson.build | 43 +++++++++++++++++++++++++++++++++++
> python/qemu/qmp/qmp_tui.py | 12 +++++-----
> python/qemu/utils/qom_fuse.py | 2 +-
> python/scripts/__init__.py | 0
> python/setup.cfg | 8 -------
> scripts/meson.build | 9 ++++++++
> tests/meson.build | 1 +
> tests/python/meson.build | 17 ++++++++++++++
> 9 files changed, 78 insertions(+), 15 deletions(-)
> create mode 100644 python/meson.build
> create mode 100644 python/scripts/__init__.py
> create mode 100644 tests/python/meson.build
>
> --
> 2.47.1
>
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:[~2025-04-14 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 19:11 [RFC 0/2] python: integrate linter tests natively with meson Daniel P. Berrangé
2025-02-24 19:11 ` [RFC 1/2] python: be more selective in hiding mypy subclassing warning Daniel P. Berrangé
2025-04-15 10:48 ` Thomas Huth
2025-02-24 19:11 ` [RFC 2/2] python: integrate linter tests natively with meson Daniel P. Berrangé
2025-02-25 6:04 ` [RFC 0/2] " Markus Armbruster
2025-02-25 12:07 ` Daniel P. Berrangé
2025-02-25 12:39 ` Markus Armbruster
2025-04-14 16:14 ` 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=Z_00erYFFJ0EPMFa@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.