qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Markus Armbruster <armbru@redhat.com>,
	 Peter Maydell <peter.maydell@linaro.org>,
	Cleber Rosa <crosa@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	qemu-discuss@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: QEMU 5.1: Can we require each new device/machine to provided a test?
Date: Tue, 7 Apr 2020 12:59:30 +0200	[thread overview]
Message-ID: <CAAdtpL7gSqz+R5LfbvsuxeeCzf1K-omHSeYo2eTOFYaMS1bp6A@mail.gmail.com> (raw)

Hello,

Following Markus thread on deprecating unmaintained (untested) code
(machines) [1] and the effort done to gather the information shared in
the replies [2], and the various acceptance tests added, is it
feasible to require for the next release that each new device/machine
is provided a test covering it?

If no, what is missing?

Thanks,

Phil.

[1] https://www.mail-archive.com/qemu-devel@nongnu.org/msg604682.html
[2] https://wiki.qemu.org/Testing/Acceptance#Machines


             reply	other threads:[~2020-04-07 11:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 10:59 Philippe Mathieu-Daudé [this message]
2020-05-15 10:11 ` QEMU 5.1: Can we require each new device/machine to provided a test? Thomas Huth
2020-05-15 10:23   ` Daniel P. Berrangé
2020-05-18 19:56     ` John Snow
2020-05-19  9:04       ` Daniel P. Berrangé
2020-05-19 23:06         ` John Snow
2020-05-20  6:13           ` Thomas Huth
2020-05-20  9:02             ` Daniel P. Berrangé
2020-05-20 14:53             ` John Snow
2020-05-20  8:57           ` Daniel P. Berrangé
2020-05-15 10:51   ` Gerd Hoffmann
2020-05-15 11:24     ` Paolo Bonzini

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=CAAdtpL7gSqz+R5LfbvsuxeeCzf1K-omHSeYo2eTOFYaMS1bp6A@mail.gmail.com \
    --to=f4bug@amsat.org \
    --cc=armbru@redhat.com \
    --cc=crosa@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=ehabkost@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.org \
    --cc=thuth@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).