From: "Andreas Färber" <afaerber@suse.de>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: thuth@redhat.com, ehabkost@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 1/7] tests: Fix how qom-test is run
Date: Tue, 29 Sep 2015 18:06:13 +0200 [thread overview]
Message-ID: <560AB6F5.4080308@suse.de> (raw)
In-Reply-To: <1443470907-32335-2-git-send-email-armbru@redhat.com>
Am 28.09.2015 um 22:08 schrieb Markus Armbruster:
> We want to run qom-test for every architecture, without having to
> manually add it to every architecture's list of tests. Commit 3687d53
> accomplished this by adding it to every architecture's list
> automatically.
>
> However, some architectures inherit their tests from others, like this:
>
> check-qtest-x86_64-y = $(check-qtest-i386-y)
> check-qtest-microblazeel-y = $(check-qtest-microblaze-y)
> check-qtest-xtensaeb-y = $(check-qtest-xtensa-y)
>
> For such architectures, we ended up running the (slow!) test twice.
> Commit 2b8419c attempted to avoid this by adding the test only when
> it's not already present. Works only as long as we consider adding
> the test to the architectures on the left hand side *after* the ones
> on the right hand side: x86_64 after i386, microblazeel after
> microblaze, xtensaeb after xtensa.
>
> Turns out we consider them in $(SYSEMU_TARGET_LIST) order. Defined as
>
> SYSEMU_TARGET_LIST := $(subst -softmmu.mak,,$(notdir \
> $(wildcard $(SRC_PATH)/default-configs/*-softmmu.mak)))
>
> On my machine, this results in the oder xtensa, x86_64, microblazeel,
> microblaze, i386. Consequently, qom-test runs twice for microblazeel
> and x86_64.
>
> Replace this complex and flawed machinery with a much simpler one: add
> generic tests (currently just qom-test) to check-qtest-generic-y
> instead of check-qtest-$(target)-y for every target, then run
> $(check-qtest-generic-y) for every target.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> tests/Makefile | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
Looks good to me,
Reviewed-by: Andreas Färber <afaerber@suse.de>
However one comment regarding your commit message: You missed that I
proposed a different patch before Peter committed his. I wonder whether
mine had the same issue...
BTW there's an old patch from Stefan H. on the list (that I have on my
queue to revisit, help appreciated), to make QTests more verbose even
without V=1.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-09-29 16:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 20:08 [Qemu-devel] [PATCH v4 0/7] Fix device introspection regressions Markus Armbruster
2015-09-28 20:08 ` [Qemu-devel] [PATCH v4 1/7] tests: Fix how qom-test is run Markus Armbruster
2015-09-29 16:06 ` Andreas Färber [this message]
2015-10-01 5:41 ` Markus Armbruster
2015-09-28 20:08 ` [Qemu-devel] [PATCH v4 2/7] libqtest: Clean up unused QTestState member sigact_old Markus Armbruster
2015-09-28 20:08 ` [Qemu-devel] [PATCH v4 3/7] libqtest: New hmp() & friends Markus Armbruster
2015-09-29 6:38 ` Thomas Huth
2015-09-29 12:41 ` Markus Armbruster
2015-09-28 20:08 ` [Qemu-devel] [PATCH v4 4/7] device-introspect-test: New, covering device introspection Markus Armbruster
2015-09-28 20:08 ` [Qemu-devel] [PATCH v4 5/7] qmp: Fix device-list-properties not to crash for abstract device Markus Armbruster
2015-09-29 6:50 ` Thomas Huth
2015-09-29 12:44 ` Markus Armbruster
2015-09-29 16:07 ` Andreas Färber
2015-09-28 20:08 ` [Qemu-devel] [PATCH v4 6/7] qdev: Protect device-list-properties against broken devices Markus Armbruster
2015-09-28 20:15 ` Eduardo Habkost
2015-09-29 7:01 ` Thomas Huth
2015-09-29 16:22 ` Andreas Färber
2015-10-01 5:45 ` Markus Armbruster
2015-09-28 20:08 ` [Qemu-devel] [PATCH v4 7/7] Revert "qdev: Use qdev_get_device_class() for -device <type>, help" Markus Armbruster
2015-09-29 15:33 ` [Qemu-devel] [PATCH v4 0/7] Fix device introspection regressions Markus Armbruster
2015-10-01 13:42 ` 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=560AB6F5.4080308@suse.de \
--to=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=ehabkost@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 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).