From: "Alex Bennée" <alex.bennee@linaro.org>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH v3 0/6] Enable more iotests during "make check-block"
Date: Tue, 22 Oct 2019 14:48:28 +0100 [thread overview]
Message-ID: <877e4wx55f.fsf@linaro.org> (raw)
In-Reply-To: <123b2e94-3f43-1a8e-2420-12ae09483e2f@redhat.com>
Max Reitz <mreitz@redhat.com> writes:
> On 22.10.19 15:11, Alex Bennée wrote:
>>
>> Thomas Huth <thuth@redhat.com> writes:
>>
>>> As discussed here:
>>>
>>> https://lists.gnu.org/archive/html/qemu-devel/2019-10/msg00697.html
>>>
>>> and here:
>>>
>>> https://lists.gnu.org/archive/html/qemu-devel/2019-10/msg01388.html
>>
>> Queued to testing/next, thanks.
>
> It should be noted that this series depends on my SOCK_DIR series (which
> I have in my block branch), or the newly added tests are likely to fail
> in the CI environment.
Ahh I misread....
<snip>
>>> it would be good to have some more valuable iotests enabled in the
>>> "auto" group to get better iotest coverage during "make check".
>>>
>>> And once Max' "iotests: Add and use $SOCK_DIR" patch series has been
>>> merged, we can indeed enable these Python-based tests, too.
I though these weren't enabled in this series. Do I need to drop all the
patches?
--
Alex Bennée
next prev parent reply other threads:[~2019-10-22 14:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 7:21 [PATCH v3 0/6] Enable more iotests during "make check-block" Thomas Huth
2019-10-22 7:21 ` [PATCH v3 1/6] iotests: remove 'linux' from default supported platforms Thomas Huth
2019-10-22 7:21 ` [PATCH v3 2/6] iotests: Test 041 only works on certain systems Thomas Huth
2019-10-22 7:21 ` [PATCH v3 3/6] iotests: Test 183 does not work on macOS and OpenBSD Thomas Huth
2019-10-22 7:21 ` [PATCH v3 4/6] iotests: Skip "make check-block" if QEMU does not support virtio-blk Thomas Huth
2019-10-30 11:21 ` Max Reitz
2019-11-11 14:02 ` Thomas Huth
2019-11-11 16:10 ` Max Reitz
2019-10-22 7:21 ` [PATCH v3 5/6] iotests: Enable more tests in the 'auto' group to improve test coverage Thomas Huth
2019-10-24 11:14 ` Alex Bennée
2019-11-27 14:11 ` Thomas Huth
2019-10-22 7:21 ` [PATCH v3 6/6] iotests: Remove 130 from the "auto" group Thomas Huth
2019-10-22 7:58 ` [PATCH v3 0/6] Enable more iotests during "make check-block" Thomas Huth
2019-10-22 11:39 ` Alex Bennée
2019-10-22 11:46 ` Thomas Huth
2019-10-22 13:09 ` Alex Bennée
2019-10-22 13:11 ` Alex Bennée
2019-10-22 13:39 ` Max Reitz
2019-10-22 13:48 ` Alex Bennée [this message]
2019-10-22 18:54 ` Thomas Huth
2019-10-22 21:16 ` Alex Bennée
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=877e4wx55f.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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.