From: Thomas Huth <thuth@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 2/5] iotests: Test 041 does not work on macOS
Date: Mon, 21 Oct 2019 10:08:48 +0200 [thread overview]
Message-ID: <9cb10562-2ae7-596b-8a37-77e82759a8fd@redhat.com> (raw)
In-Reply-To: <cacfc0c2-cdb4-fded-e317-a51d38cc512c@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1789 bytes --]
On 18/10/2019 18.19, Max Reitz wrote:
> On 11.10.19 16:50, Thomas Huth wrote:
>> 041 works fine on Linux, FreeBSD and OpenBSD, so let's mark it as
>> only supported on these systems.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> tests/qemu-iotests/041 | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/tests/qemu-iotests/041 b/tests/qemu-iotests/041
>> index 8568426311..7211f1950a 100755
>> --- a/tests/qemu-iotests/041
>> +++ b/tests/qemu-iotests/041
>> @@ -1123,4 +1123,5 @@ class TestOrphanedSource(iotests.QMPTestCase):
>>
>> if __name__ == '__main__':
>> iotests.main(supported_fmts=['qcow2', 'qed'],
>> - supported_protocols=['file'])
>> + supported_protocols=['file'],
>> + supported_platforms=['linux', 'freebsd', 'openbsd6'])
>
> Hmm, why not just “openbsd”, or single out macOS as unsupported? (I
> suppose the latter would require an additional patch.)
Ah, right, John's patch uses "startswith(x)", so just using 'openbsd'
should work fine, too. (I initially thought that I have to use the exact
string here)
> There’s also the fact that I maybe wanted to let make check skip all
> tests on macOS and Windows – though that doesn’t make this patch
> unnecessary, because that would only fix make check, not running the
> iotests explicitly.
>
> And I suppose maybe we even want to run the tests in macOS if it’s part
> of the CI anyway?
At least the current set of tests in the "auto" group works fine on
macOS (running on Cirrus-CI and Travis), so I think we should keep it
enabled in the CI for now (until it creates too much trouble and nobody
is able to debug it ... but we're not at that point yet).
Thomas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-10-21 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 14:50 [PATCH 0/5] Enable more iotests during "make check-block" Thomas Huth
2019-10-11 14:50 ` [PATCH 1/5] iotests: remove 'linux' from default supported platforms Thomas Huth
2019-10-18 16:15 ` Max Reitz
2019-10-11 14:50 ` [PATCH 2/5] iotests: Test 041 does not work on macOS Thomas Huth
2019-10-18 16:19 ` Max Reitz
2019-10-21 8:08 ` Thomas Huth [this message]
2019-10-11 14:50 ` [PATCH 3/5] iotests: Test 183 does not work on macOS and OpenBSD Thomas Huth
2019-10-11 14:50 ` [PATCH 4/5] iotests: Skip "make check-block" if QEMU does not support virtio-blk Thomas Huth
2019-10-14 11:21 ` Kevin Wolf
2019-10-14 11:27 ` Thomas Huth
2019-10-14 14:17 ` Kevin Wolf
2019-10-18 17:08 ` Max Reitz
2019-10-11 14:50 ` [PATCH 5/5] iotests: Enable more tests in the 'auto' group to improve test coverage Thomas Huth
2019-10-18 17:13 ` 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=9cb10562-2ae7-596b-8a37-77e82759a8fd@redhat.com \
--to=thuth@redhat.com \
--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 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).