From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] iotests: Skip 181 and 201 without userfaultfd
Date: Mon, 16 Apr 2018 13:51:04 +0200 [thread overview]
Message-ID: <55f6042f-f077-1860-877f-adb57db254ad@redhat.com> (raw)
In-Reply-To: <20180406151731.4285-1-mreitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
On 2018-04-06 17:17, Max Reitz wrote:
> My non-Fedora testing system does not have a kernel with userfaultfd
> support which causes 181 and 201 to fail. That is annoying. This
> series makes those tests recognize the issue and convert it into a
> _notrun.
>
>
> Max Reitz (2):
> iotests: Add failure matching to common.qemu
> iotests: Skip 181 and 201 without userfaultfd
>
> tests/qemu-iotests/181 | 13 ++++++++++
> tests/qemu-iotests/201 | 13 ++++++++++
> tests/qemu-iotests/common.qemu | 58 +++++++++++++++++++++++++++++++++++++-----
> 3 files changed, 77 insertions(+), 7 deletions(-)
Ping (considering these are test suite fixes, I'd merge them without
review, too, though.)
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-04-16 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 15:17 [Qemu-devel] [PATCH 0/2] iotests: Skip 181 and 201 without userfaultfd Max Reitz
2018-04-06 15:17 ` [Qemu-devel] [PATCH 1/2] iotests: Add failure matching to common.qemu Max Reitz
2018-04-06 15:17 ` [Qemu-devel] [PATCH 2/2] iotests: Skip 181 and 201 without userfaultfd Max Reitz
2018-04-06 15:30 ` [Qemu-devel] [PATCH 0/2 for-2.12?] " Eric Blake
2018-04-06 15:34 ` Max Reitz
2018-04-16 11:51 ` Max Reitz [this message]
2018-04-20 19:35 ` [Qemu-devel] [PATCH 0/2] " Max Reitz
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=55f6042f-f077-1860-877f-adb57db254ad@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@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 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).