From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Michael Roth" <michael.roth@amd.com>
Subject: Re: [PATCH] tests: Move unit tests into a separate directory
Date: Wed, 10 Mar 2021 10:22:51 +0100 [thread overview]
Message-ID: <04db468c-825a-941c-038a-f7d7c7e00c01@redhat.com> (raw)
In-Reply-To: <942499e4-0a67-ff9a-08e8-ac7d3cbc3c21@redhat.com>
On 10/03/2021 10.11, Paolo Bonzini wrote:
> On 10/03/21 10:08, Thomas Huth wrote:
>>>
>>> Looks good, I would have moved benchmarks as well but anyway it can be
>>> done separately.
>>
>> My plan is to move them into a separate directory (tests/bench/) since
>> this is a separate test suite.
>
> That makes sense indeed.
>
>> By the way, "make check-speed" is not working for me anymore (but "make
>> bench" is working fine) ... and I haven't found out yet what's wrong ...
>> is it working for you?
>
> No; "make bench" and "make bench-speed" work though.
It's because this filter logic in the generated Makefile.mtest:
bench-speed: run-tests
ifneq ($(filter bench-speed bench, $(MAKECMDGOALS)),)
.tests += $(.test.$(SPEED).bench-speed)
endif
all-bench-targets += bench-speed
... so a quick fix is:
diff a/tests/Makefile.include b/tests/Makefile.include
--- a/tests/Makefile.include
+++ b/tests/Makefile.include
@@ -156,6 +156,7 @@ clean: check-clean
# For backwards compatibility
-check-speed: bench-speed
+check-speed:
+ $(MAKE) bench-speed
endif
Thomas
next prev parent reply other threads:[~2021-03-10 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 6:33 [PATCH] tests: Move unit tests into a separate directory Thomas Huth
2021-03-10 8:15 ` Paolo Bonzini
2021-03-10 9:08 ` Thomas Huth
2021-03-10 9:11 ` Paolo Bonzini
2021-03-10 9:22 ` Thomas Huth [this message]
2021-03-10 10:21 ` Paolo Bonzini
2021-03-10 10:32 ` Markus Armbruster
2021-03-10 10:36 ` Paolo Bonzini
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=04db468c-825a-941c-038a-f7d7c7e00c01@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--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 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).