From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Cleber Rosa" <crosa@redhat.com>, "Kevin Wolf" <kwolf@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Caio Carrara" <ccarrara@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] Acceptance tests for qemu-img
Date: Tue, 13 Nov 2018 13:50:24 +0000 [thread overview]
Message-ID: <20181113135024.GI14591@redhat.com> (raw)
In-Reply-To: <875zx18geq.fsf@dusky.pond.sub.org>
On Tue, Nov 13, 2018 at 10:39:57AM +0100, Markus Armbruster wrote:
> Drive-by comment...
>
> Cleber Rosa <crosa@redhat.com> writes:
>
> [...]
> > My impression is that the "infrastructure for block tests" is not that
> > different from the infrastructure needed by other tests, specially other
> > QEMU tests.
> [...]
>
> Yes. The actual reason for having a completely separate testing
> infrastructure for block tests is that it predates testing
> infrastructure for anything else.
>
> Moving the tests to common infrastructure would be a sizable one-time
> effort we can ill afford. Maintaining multiple testing infrastructures
> is an ongoing effort we can also ill afford.
If we do want to move to a common infrastructure, then IMHO this patch
series should do the work to convert qemu-iotests to use it.
Currently this is simply introducing a 2nd way to write block tests.
We know from bitter experiance that when we introduce a new system in
QEMU without converting the old system, the old system will live forever
increasing our maint burden & creatnig confusion for developers about
which is the preferred approach.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-11-13 13:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 22:12 [Qemu-devel] [RFC PATCH 0/2] Acceptance tests for qemu-img Cleber Rosa
2018-11-09 22:12 ` [Qemu-devel] [RFC PATCH 1/2] Acceptance Tests: add QemuImgTest base class Cleber Rosa
2018-11-09 22:12 ` [Qemu-devel] [RFC PATCH 2/2] qemu-img: consider a zero number of I/O requests an invalid count Cleber Rosa
2018-11-12 14:38 ` Philippe Mathieu-Daudé
2018-11-12 15:04 ` Cleber Rosa
2018-11-12 10:49 ` [Qemu-devel] [RFC PATCH 0/2] Acceptance tests for qemu-img Kevin Wolf
2018-11-12 14:59 ` Cleber Rosa
2018-11-12 15:11 ` Daniel P. Berrangé
2018-11-12 16:00 ` Kevin Wolf
2018-11-12 17:36 ` Cleber Rosa
2018-11-13 9:39 ` Markus Armbruster
2018-11-13 13:50 ` Daniel P. Berrangé [this message]
2018-11-13 14:41 ` Cleber Rosa
2018-11-13 12:18 ` Kevin Wolf
2018-11-13 13:26 ` Eduardo Habkost
2018-11-13 13:51 ` Kevin Wolf
2018-11-13 13:56 ` Eduardo Habkost
2018-11-13 14:20 ` Cleber Rosa
2018-11-13 14:32 ` Eduardo Habkost
2018-11-13 14:43 ` Cleber Rosa
2018-11-13 14:51 ` Eduardo Habkost
2018-11-13 14:15 ` Cleber Rosa
2018-11-13 15:38 ` Kevin Wolf
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=20181113135024.GI14591@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=ccarrara@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.com \
/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).