From: Thomas Huth <thuth@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Victor Kaplansky" <victork@redhat.com>,
qemu-block@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-s390x@nongnu.org, "Hervé Poussineau" <hpoussin@reactos.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/3] Add new CD-ROM related qtests
Date: Mon, 2 Apr 2018 21:43:52 +0200 [thread overview]
Message-ID: <cb2451b1-fa49-cc6c-4398-5cf7e8963924@redhat.com> (raw)
In-Reply-To: <316190e9-552f-23c8-e9e6-2b24f708ae7c@redhat.com>
On 02.04.2018 21:34, John Snow wrote:
>
>
> On 04/02/2018 02:39 PM, Thomas Huth wrote:
>> On 29.03.2018 20:28, John Snow wrote:
>>>
>>>
>>> On 03/16/2018 01:39 AM, Thomas Huth wrote:
>>>> With one of my clean-up patches (see commit 1454509726719e0933c800), I
>>>> recently accidentially broke the "-cdrom" parameter (more precisely
>>>> "-drive if=scsi") on a couple of boards, since there was no error
>>>> detected during the "make check" regression testing. This is clearly an
>>>> indication that we are lacking tests in this area.
>>>> So this small patch series now introduces some tests for CD-ROM drives:
>>>> The first two patches introduce the possibility to check that booting
>>>> from CD-ROM drives still works fine for x86 and s390x, and the third
>>>> patch adds a test that certain machines can at least still be started
>>>> with the "-cdrom" parameter (i.e. that test would have catched the
>>>> mistake that I did with my SCSI cleanup patch).
>>>>
>>>> v2:
>>>> - Use g_spawn_sync() instead of execlp() to run genisoimage
>>>> - The "-cdrom" parameter test is now run on all architectures (with
>>>> machine "none" for the machines that are not explicitly checked)
>>>> - Some rewordings and improved comments here and there
>>>>
>>>> Thomas Huth (3):
>>>> tests/boot-sector: Add magic bytes to s390x boot code header
>>>> tests/cdrom-test: Test booting from CD-ROM ISO image file
>>>> tests/cdrom-test: Test that -cdrom parameter is working
>>>>
>>>> tests/Makefile.include | 2 +
>>>> tests/boot-sector.c | 9 +-
>>>> tests/cdrom-test.c | 222 +++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 3 files changed, 230 insertions(+), 3 deletions(-)
>>>> create mode 100644 tests/cdrom-test.c
>>>>
>>>
>>> New file, but no edit to MAINTAINERS.
>>
>> Which section do you suggest? It tests IDE CD-ROMs, SCSI CD-ROMs, and
>> even virtio-block (on s390x) ... so I have a hard time to decide where
>> this should belong to...
>>
>> Thomas
>>
>
> I was hoping you'd figure it out, but fine :D
>
> You can stick it under my section if you want, but I'll probably defer
> to you if the s390x parts break.
Ok, thanks. But in the long run, we might even need a generic "QTESTS"
section in the MAINTAINERS file, since most of the qtests are currently
not listed there.
And while we're at it, we should maybe also move the qtests to a
separate folder tests/qtests/ or so, so that it is clearer which of the
tests is a qtest and which are something different.
I'll try to come up with some patches once the hard freeze is over...
Thomas
prev parent reply other threads:[~2018-04-02 19:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 5:39 [Qemu-devel] [PATCH v2 0/3] Add new CD-ROM related qtests Thomas Huth
2018-03-16 5:39 ` [Qemu-devel] [PATCH v2 1/3] tests/boot-sector: Add magic bytes to s390x boot code header Thomas Huth
2018-03-16 11:58 ` Philippe Mathieu-Daudé
2018-03-16 5:39 ` [Qemu-devel] [PATCH v2 2/3] tests/cdrom-test: Test booting from CD-ROM ISO image file Thomas Huth
2018-03-16 11:58 ` Philippe Mathieu-Daudé
2018-03-16 5:39 ` [Qemu-devel] [PATCH v2 3/3] tests/cdrom-test: Test that -cdrom parameter is working Thomas Huth
2018-03-16 5:54 ` [Qemu-devel] [PATCH v2 0/3] Add new CD-ROM related qtests Hervé Poussineau
2018-03-16 11:01 ` Mark Cave-Ayland
2018-03-16 12:56 ` Michael S. Tsirkin
2018-03-29 18:28 ` John Snow
2018-04-02 18:39 ` Thomas Huth
2018-04-02 19:34 ` John Snow
2018-04-02 19:43 ` Thomas Huth [this message]
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=cb2451b1-fa49-cc6c-4398-5cf7e8963924@redhat.com \
--to=thuth@redhat.com \
--cc=f4bug@amsat.org \
--cc=hpoussin@reactos.org \
--cc=jsnow@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=victork@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).