From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, Mads Ynddal <mads@ynddal.dk>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2] tests/tracetool: Honor the Python interpreter that "configure" detected
Date: Thu, 15 Jan 2026 15:56:54 +0000 [thread overview]
Message-ID: <aWkORqBqOXu6eSpQ@redhat.com> (raw)
In-Reply-To: <20260115155318.37823-1-thuth@redhat.com>
On Thu, Jan 15, 2026 at 04:53:18PM +0100, Thomas Huth wrote:
> From: Thomas Huth <thuth@redhat.com>
>
> The tracetool tests currently fail if the host installation does not
> have a "python3" binary (and you compiled QEMU by selecting a different
> one during the "configure" step). This happens because tracetool-test.py
> executes scripts/tracetool.py directly, so that this script is run via
> its shebang line. To fix the issue, use the same Python interpreter to
> run scripts/tracetool.py as we are using to run the tracetool-test.py
> script.
>
> Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> v2: Use sys.executable instead of passing the Python interpreter around
> via a PYTHON environment variable.
>
> tests/tracetool/tracetool-test.py | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
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 :|
next prev parent reply other threads:[~2026-01-15 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 15:53 [PATCH v2] tests/tracetool: Honor the Python interpreter that "configure" detected Thomas Huth
2026-01-15 15:56 ` Daniel P. Berrangé [this message]
2026-01-19 19:04 ` Stefan Hajnoczi
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=aWkORqBqOXu6eSpQ@redhat.com \
--to=berrange@redhat.com \
--cc=mads@ynddal.dk \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@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 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.