All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: "Christian Quante" <christian@quante.one>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	John Snow <jsnow@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 0/3] tests/qtest/fdc-test: give each test case its own instance
Date: Thu, 03 Sep 2026 10:55:53 -0300	[thread overview]
Message-ID: <87mrtyh21i.fsf@suse.de> (raw)
In-Reply-To: <20260824112307.223856-1-christian@quante.one>

Christian Quante <christian@quante.one> writes:

> Hi Marc-André,
>
> thanks for testing it.
>
>> Series lgtm, however it takes ~10s more now.
>
> I can't reproduce that here: fdc-test goes from 0.8s to 2.6s, so
> +1.8s. With an --enable-asan build it is 3.4s, still nowhere near
> +10s. The series takes the test from 2 QEMU instances to 16, at about
> 128ms each.
>
> What are you measuring, and on what kind of build -- fdc-test on its
> own?
>
> Christian

The timing looks ok on my side as well. I'll queue this series for the
moment. @Marc-André, feel free to object.

Thanks!


  reply	other threads:[~2026-09-03 13:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 10:43 [PATCH 0/3] tests/qtest/fdc-test: give each test case its own instance Christian Quante
2026-08-22 10:43 ` [PATCH 1/3] tests/qtest/fdc-test: give each test case its own QEMU instance Christian Quante
2026-08-22 10:43 ` [PATCH 2/3] tests/qtest/fdc-test: skip test cases when the 'pc' machine is missing Christian Quante
2026-08-22 10:43 ` [PATCH 3/3] tests/qtest/fdc-test: check that READ ID answers for the drive it names Christian Quante
2026-08-24  9:47 ` [PATCH 0/3] tests/qtest/fdc-test: give each test case its own instance Marc-André Lureau
2026-08-24 11:23   ` Christian Quante
2026-09-03 13:55     ` Fabiano Rosas [this message]
2026-09-03 20:29       ` Marc-André Lureau

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=87mrtyh21i.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=christian@quante.one \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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 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.