From: Thomas Huth <thuth@redhat.com>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>, qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
qemu-arm@nongnu.org, qemu-ppc@nongnu.org, qemu-s390x@nongnu.org,
qemu-riscv@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [RFC PATCH] tests/functional: Move tests into architecture specific folders
Date: Fri, 11 Jul 2025 13:55:20 +0200 [thread overview]
Message-ID: <8f90fbd7-1edd-45cc-9540-06fd9d0ee978@redhat.com> (raw)
In-Reply-To: <643f1db1-4a7a-4bc0-a187-9ff1561f8a3d@linaro.org>
On 10/07/2025 17.51, Pierrick Bouvier wrote:
> On 7/10/25 2:42 AM, Thomas Huth wrote:
>> This patch tackles two issues. First, the tests/functional folder has
>> become quite crowded already, some restructuring would be helpful here.
>> Second, we currently encode the target architecture twice in the test
>> names since a lot of the test file names contain the target, too.
>> This contributes to the very long output lines when running "make
>> check-functional".
>>
>
> I agree with the "crowded" aspect of functional tests, and subfolders are
> definitely welcome.
>
> Concerning the long line, it seems that setup ("thorough" in this example)
> is repeated 3 times on it, which is a bigger issue than having arch name
> being repeated.
>
> A simpler solution for the "long line" issue would be to change
> mtest2make.py to generate shorter test target names. This would not benefit
> for using meson test directly, but from what I understood, this is not
> recommended nor supported anyway.
I agree that this is a bigger annoyance here, but as far as I understood
that that repeated "thorough" term is just a listing of all the test suites
that the test is part of. I think this would rather need to be fixed on the
meson test runner side - why does meson list all test suites here? The one
that applies to the current should be enough, shouldn't it?
Thomas
next prev parent reply other threads:[~2025-07-11 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 9:42 [RFC PATCH] tests/functional: Move tests into architecture specific folders Thomas Huth
2025-07-10 9:59 ` Manos Pitsidianakis
2025-07-10 12:18 ` Thomas Huth
2025-07-10 14:50 ` Daniel P. Berrangé
2025-07-11 11:51 ` Thomas Huth
2025-07-10 15:51 ` Pierrick Bouvier
2025-07-11 11:55 ` Thomas Huth [this message]
2025-07-11 16:15 ` Pierrick Bouvier
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=8f90fbd7-1edd-45cc-9540-06fd9d0ee978@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=qemu-s390x@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 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).