From: Paolo Bonzini <pbonzini@redhat.com>
To: Claudio Fontana <cfontana@suse.de>
Cc: Richard Henderson <richard.henderson@linaro.org>,
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: Fri, 9 Oct 2020 19:10:35 +0200 [thread overview]
Message-ID: <f4fd629b-3f19-3cd0-f15f-94ee81060f08@redhat.com> (raw)
In-Reply-To: <41cce7d1-ed3e-46ff-aaee-98ded342f6a2@suse.de>
On 09/10/20 15:32, Claudio Fontana wrote:
>> QTEST_QEMU_IMG=./qemu-img \
>> G_TEST_DBUS_DAEMON=/home/pbonzini/work/upstream/qemu/tests/dbus-vmstate-daemon.sh \
>> QTEST_QEMU_BINARY=./qemu-system-x86_64 \
>> tests/qtest/bios-tables-test --tap -k
>>
>> Paolo
>>
> Hi Paolo,
>
> I now just found out that bios-tables-test actually was segfaulting
Yes, that's what "too few tests run" usually means.
Paolo
next prev parent reply other threads:[~2020-10-09 17:16 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
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 [this message]
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=f4fd629b-3f19-3cd0-f15f-94ee81060f08@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cfontana@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).