From: Claudio Fontana <cfontana@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Alex Bennee <alex.bennee@linaro.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: does make check now require TCG? Or is it a parallelism issue?
Date: Thu, 8 Oct 2020 17:34:52 +0200 [thread overview]
Message-ID: <e6300199-39e3-4f11-d97e-e2e7d9a9e8ef@suse.de> (raw)
In-Reply-To: <569520f6-adf6-6212-9625-a184bf499e24@redhat.com>
On 10/8/20 5:02 PM, Paolo Bonzini wrote:
> On 08/10/20 16:48, Claudio Fontana wrote:
>> on master, a build without tcg like:
>>
>> exec '../configure' '--disable-tcg' '--enable-kvm' '--enable-hax' "$@"
>>
>> make -j120 check
>> Generating qemu-version.h with a meson_exe.py custom command
>> make: *** No rule to make target 'qemu-system-aarch64', needed by 'check-block'. Stop.
>> make: *** Waiting for unfinished jobs....
>>
>> qemu-system-aarch64 is required for check-block now?
>
> No, it's not, it's an unnecessary dependency. This will fix it:
>
> diff --git a/tests/Makefile.include b/tests/Makefile.include
> index 5aca98e60c..1ca70d88ce 100644
> --- a/tests/Makefile.include
> +++ b/tests/Makefile.include
> @@ -140,7 +140,7 @@ QEMU_IOTESTS_HELPERS-$(CONFIG_LINUX) = tests/qemu-iotests/socket_scm_helper$(EXE
> check: check-block
> check-block: $(SRC_PATH)/tests/check-block.sh qemu-img$(EXESUF) \
> qemu-io$(EXESUF) qemu-nbd$(EXESUF) $(QEMU_IOTESTS_HELPERS-y) \
> - $(patsubst %-softmmu,qemu-system-%,$(filter %-softmmu,$(TARGET_DIRS)))
> + qemu-system-$(patsubst ppc64%,ppc64, $(shell uname -m))
> @$<
> endif
>
>
>
thanks this works!
>> If I run without -j:
>>
>> Running test qtest-i386: qmp-cmd-test
>> Broken pipe
>> ../tests/qtest/libqtest.c:175: kill_qemu() detected QEMU death from signal 6 (Aborted) (core dumped)
>> ERROR qtest-i386: qmp-cmd-test - too few tests run (expected 53, got 45)
>> make: *** [Makefile.mtest:1074: run-test-151] Error 1
>
> This one is different and I've never seen it.
This one seems an additional, non-tcg build only error, will update when I have more details.
>
> Paolo
>
Ciao,
Claudio
next prev parent reply other threads:[~2020-10-08 15:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 14:48 does make check now require TCG? Or is it a parallelism issue? Claudio Fontana
2020-10-08 15:02 ` Paolo Bonzini
2020-10-08 15:34 ` Claudio Fontana [this message]
2020-10-08 16:25 ` Claudio Fontana
2020-10-08 16:31 ` Paolo Bonzini
2020-10-08 16:35 ` Claudio Fontana
2020-10-08 16:51 ` Claudio Fontana
2020-10-09 9:23 ` Philippe Mathieu-Daudé
2020-10-09 9:40 ` Claudio Fontana
2020-10-09 10:35 ` Pavel Dovgalyuk
2020-10-09 11:46 ` Paolo Bonzini
2020-10-08 17:44 ` Richard Henderson
2020-10-08 17:53 ` Claudio Fontana
2020-10-08 18:05 ` Richard Henderson
2020-10-08 18:24 ` Paolo Bonzini
2020-10-08 21:07 ` Claudio Fontana
2020-10-09 7:40 ` Paolo Bonzini
2020-10-09 10:28 ` Claudio Fontana
2020-10-09 11:49 ` Paolo Bonzini
2020-10-09 12:13 ` Peter Maydell
2020-10-09 13:32 ` Claudio Fontana
2020-10-09 17:10 ` Paolo Bonzini
2020-10-09 7:21 ` Thomas Huth
2020-10-09 7:37 ` Paolo Bonzini
2020-10-09 9:25 ` Philippe Mathieu-Daudé
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=e6300199-39e3-4f11-d97e-e2e7d9a9e8ef@suse.de \
--to=cfontana@suse.de \
--cc=alex.bennee@linaro.org \
--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).