From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Emmanuel Blot" <eblot@meta.com>,
qemu-devel@nongnu.org, "Thomas Huth" <th.huth+qemu@posteo.eu>,
"Philippe Mathieu-Daudé" <philmd@mailo.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Laurent Vivier" <lvivier@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] tests: strip macOS "-unsigned" suffix from binary name
Date: Mon, 8 Jun 2026 16:35:12 +0100 [thread overview]
Message-ID: <aibhMPHu6nbBT3Yi@redhat.com> (raw)
In-Reply-To: <CAFEAcA-aNmOmjhbVypCLpDVowTeSK-28aaY5X0jqRe32qmkqUQ@mail.gmail.com>
On Mon, Jun 08, 2026 at 04:29:47PM +0100, Peter Maydell wrote:
> On Mon, 8 Jun 2026 at 16:25, Emmanuel Blot <eblot@meta.com> wrote:
> >
> > On macOS, plain QEMU binaries are named qemu-system-<arch>-unsigned.
> >
> > In libqtest, qtest_get_arch() extracts the architecture by splitting
> > after "-system-", which yields "arm-unsigned" instead of "arm". This
> > prevents the QOS graph from matching any machine node, causing all
> > QOS-based tests to be silently skipped.
> >
> > In the functional test framework, the same suffix causes the arch to
> > be parsed as "unsigned", leading to wrong output directories and
> > teardown failures.
> >
> > Strip the "-unsigned" suffix on both code paths.
> >
> > Signed-off-by: Emmanuel Blot <eblot@meta.com>
> > ---
> > Address issues with liqtest and functional test framework when run from
> > a macOS host.
> >
> > Unsigned binaries on macOS may be appended an `-unsigned` suffix, which
> > confuse these components that rely on the binary name to recover the
> > guest architecture.
>
> I still think this not the right thing to do. The "make" process
> on macos should produce and sign the binary in-place in the
> build tree, so that users and test cases don't have to care
> about this macos specific weirdness. (If the signing is
> location-specific and we need to sign again for "make install"
> that's fine. But we should produce a working binary with the
> usual name in the build tree, not a non-working one or one with a
> nonstandard name.)
Yes, I was just about to write similar when I saw your message.
We should not have this custom "-unsigned" name in the build
tree as specialcases like this break too many expectations,
especially when most devs aren't ever testing for macOS and so
won't see the special case.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-06-08 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 15:24 [PATCH] tests: strip macOS "-unsigned" suffix from binary name Emmanuel Blot
2026-06-08 15:29 ` Peter Maydell
2026-06-08 15:35 ` Daniel P. Berrangé [this message]
2026-06-08 15:38 ` Peter Maydell
2026-06-08 15:56 ` Emmanuel Blot
2026-06-08 16:08 ` Peter Maydell
2026-06-08 16:43 ` Pierrick Bouvier
2026-06-08 17:39 ` Peter Maydell
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=aibhMPHu6nbBT3Yi@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=eblot@meta.com \
--cc=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@mailo.com \
--cc=qemu-devel@nongnu.org \
--cc=th.huth+qemu@posteo.eu \
/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.