All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>,
	David Gibson <david@gibson.dropbear.id.au>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Laurent Vivier" <lvivier@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Fam Zheng" <famz@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Cleber Rosa" <crosa@redhat.com>,
	"Lukáš Doktor" <ldoktor@redhat.com>
Subject: Re: [Qemu-devel] make check speed
Date: Tue, 29 Aug 2017 18:34:08 +0200	[thread overview]
Message-ID: <c4c9776a-4284-796d-2439-42ad89015098@redhat.com> (raw)
In-Reply-To: <20170823142047.366068f7.cohuck@redhat.com>

On 23.08.2017 14:20, Cornelia Huck wrote:
> On Wed, 23 Aug 2017 10:35:43 +0200
> Thomas Huth <thuth@redhat.com> wrote:
> 
>> True. And I just learned that you can also already set the SPEED
>> variable to either "quick" or "slow" and that we're already using
>> g_test_quick() and g_test_slow() in a couple of places to check this. So
>> the framework for running quick vs. thorough tests is already there ...
>> we just might want to add this to some more tests, I guess...
>>
>> Question for the maintainers and the test automation folks: Is anybody
>> already running "make check SPEED=slow" or is this just rather an
>> unheard-of way of running the tests?
> 
> So I tried this on master just for fun, and 'make V=1 SPEED=slow
> check-qtest-x86_64' promptly failed for some ivshmem test.
> 
> On x86_86:
> TEST: tests/ivshmem-test... (pid=3672)
>   /x86_64/ivshmem/single:                                              OK
>   /x86_64/ivshmem/hotplug:                                             OK
>   /x86_64/ivshmem/memdev:                                              OK
>   /x86_64/ivshmem/pair:                                                OK
>   /x86_64/ivshmem/server-msi:                                          **
> ERROR:/home/cohuck/git/qemu/tests/ivshmem-test.c:367:test_ivshmem_server: assertion failed (ret == 0): (1 == 0)
> FAIL
> GTester: last random seed: R02Scde8fd6835fdf17450c73e2f74f25007
> (pid=3697)
>  /x86_64/ivshmem/server-irq:                                          OK
> FAIL: tests/ivshmem-test

Bisecting this problem automatically ("git bisect run" rules!) revealed
that this test broke with this commit:

	commit b4ba67d9a702507793c2724e56f98e9b0f7be02b
	Author: David Gibson <david@gibson.dropbear.id.au>
	Title: libqos: Change PCI accessors to take opaque BAR handle

David, any ideas what's going wrong here?

 Thomas

  parent reply	other threads:[~2017-08-29 16:34 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16  8:26 [Qemu-devel] [PATCH for-2.10] boot-serial-test: prefer tcg accelerator Cornelia Huck
2017-08-16  8:28 ` Laurent Vivier
2017-08-16 10:25 ` Thomas Huth
2017-08-16 10:51 ` Paolo Bonzini
2017-08-16 11:18   ` Peter Maydell
2017-08-16 11:46     ` Cornelia Huck
2017-08-22  1:09     ` David Gibson
2017-08-22  5:40       ` Thomas Huth
2017-08-22  8:47       ` Peter Maydell
2017-08-22  8:49         ` Laurent Vivier
2017-08-22  9:35           ` Peter Maydell
2017-08-22 11:20             ` David Gibson
2017-08-22 11:48               ` Cornelia Huck
2017-08-23  0:29                 ` David Gibson
2017-08-23  7:16                   ` Cornelia Huck
2017-08-23  7:49                     ` [Qemu-devel] make check speed (was: Re: [PATCH for-2.10] boot-serial-test: prefer tcg accelerator) Thomas Huth
2017-08-23  8:01                       ` [Qemu-devel] make check speed Paolo Bonzini
2017-08-23  8:35                         ` Thomas Huth
2017-08-23  8:52                           ` Fam Zheng
2017-08-23  9:09                             ` Fam Zheng
2017-08-23  9:33                           ` Paolo Bonzini
2017-08-24  3:01                             ` David Gibson
2017-08-23 11:51                           ` Lukáš Doktor
2017-08-23 12:01                             ` Thomas Huth
2017-08-23 12:13                               ` Lukáš Doktor
2017-08-24 13:52                                 ` Cleber Rosa
2017-08-23 12:35                             ` Thomas Huth
2017-08-23 12:52                               ` Lukáš Doktor
2017-08-23 12:20                           ` Cornelia Huck
2017-08-24  5:27                             ` Thomas Huth
2017-08-30  8:59                               ` Cornelia Huck
2017-08-30  9:13                                 ` Thomas Huth
2017-08-30 11:52                                   ` Markus Armbruster
2017-08-30 13:56                                     ` Thomas Huth
2017-08-30 14:19                                       ` Markus Armbruster
2017-08-29 16:34                             ` Thomas Huth [this message]
2017-08-29 17:13                               ` Thomas Huth
2017-08-16 14:03 ` [Qemu-devel] [PATCH for-2.10] boot-serial-test: prefer tcg accelerator Richard Henderson

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=c4c9776a-4284-796d-2439-42ad89015098@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=cohuck@redhat.com \
    --cc=crosa@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=f4bug@amsat.org \
    --cc=famz@redhat.com \
    --cc=ldoktor@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.