qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Claudio Fontana <cfontana@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>
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 15:32:04 +0200	[thread overview]
Message-ID: <41cce7d1-ed3e-46ff-aaee-98ded342f6a2@suse.de> (raw)
In-Reply-To: <eba000db-c0d1-8474-15cc-6fa6e864bb88@redhat.com>

On 10/9/20 1:49 PM, Paolo Bonzini wrote:
> On 09/10/20 12:28, Claudio Fontana wrote:
>> Running test qtest-x86_64: qos-test
>> ERROR qtest-x86_64: bios-tables-test - too few tests run (expected 23, got 22)
>> make: *** [Makefile.mtest:1326: run-test-187] Error 1
>> make: *** Waiting for unfinished jobs....
>>
>> What am I missing here?
> 
> This is something else that is crashing.
> 
> You want to do (as for any other test; this should be documented)
> 
>   make -j12 check-qtest V=1
> 
> and then cut-and-paste the bios-tables-test line, which should be something like
> 
>   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, but even with V=1
there was no indication or hint about it from the tests, maybe there should be?

Segfault seems to be stemming from a missing check for NULL in the free function for the test data,
with that change things seem to finally work for bios-tables-test.

Now to the next failing test.. (qos-test buzzes with no output, we'll see..)

Thanks,

Claudio





  parent reply	other threads:[~2020-10-09 13:33 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 [this message]
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=41cce7d1-ed3e-46ff-aaee-98ded342f6a2@suse.de \
    --to=cfontana@suse.de \
    --cc=alex.bennee@linaro.org \
    --cc=pbonzini@redhat.com \
    --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).