qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
	Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
	"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 1/4] iotests: add script_initialize
Date: Wed, 18 Sep 2019 14:41:56 -0400	[thread overview]
Message-ID: <59694b0e-b6c1-7dfb-818a-c82dc0f14947@redhat.com> (raw)
In-Reply-To: <2eea4fa4-cee1-9007-0ff9-784d004c2668@redhat.com>



On 9/18/19 9:05 AM, Thomas Huth wrote:
> On 18/09/2019 00.29, John Snow wrote:
>>
>>
>> On 9/16/19 10:56 AM, Vladimir Sementsov-Ogievskiy wrote:
> [...]
>>> Finally do we support something except linux for iotests?
>>> for bash tests _supported_os also used only with "Linux" in 87 tests..
> 
> The iotests in the "auto" group are supposed to work on other OSes
> beside Linux, too, since they are run automatically during "make check"
> now. You can use github with cirrus-ci to check FreeBSD and macOS, see
> e.g.: https://cirrus-ci.com/build/5114679677943808
> 
> Travis has support for macOS, too.
> 
> And to test them on OpenBSD (or FreeBSD), you can use the VM tests, e.g.
> something like this:
> 
> make vm-build-openbsd J=8 BUILD_TARGET=check-block \
>    EXTRA_CONFIGURE_OPTS=--target-list=x86_64-softmmu
> 
>> aaand lastly, running `make check` doesn't happen to call any of the
>> tests that appear broken on FreeBSD right now, so I'm just going to go
>> ahead and say we can open Pandora's box and make the default python test
>> behavior to run on any OS, and start re-blacklisting the edge-cases as
>> we find them.
> 
> Sounds good. If it breaks on FreeBSD or macOS, we'll find out with
> cirrus-ci or Travis pretty soon.
> 

Yeah. It's annoying, but genuinely the quickest way to figure it out. 
Keep an eye on the v5 of this series for fallout.

--js


  reply	other threads:[~2019-09-18 18:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-12  0:16 [Qemu-devel] [PATCH v4 0/4] iotests: use python logging John Snow
2019-09-12  0:16 ` [Qemu-devel] [PATCH v4 1/4] iotests: add script_initialize John Snow
2019-09-16 14:56   ` Vladimir Sementsov-Ogievskiy
2019-09-16 16:32     ` John Snow
2019-09-16 16:39       ` Vladimir Sementsov-Ogievskiy
2019-09-16 17:13         ` John Snow
2019-09-17 22:29     ` John Snow
2019-09-18 10:30       ` Vladimir Sementsov-Ogievskiy
2019-09-18 16:44         ` Vladimir Sementsov-Ogievskiy
2019-09-18 17:00           ` John Snow
2019-09-18 13:05       ` Thomas Huth
2019-09-18 18:41         ` John Snow [this message]
2019-09-12  0:16 ` [Qemu-devel] [PATCH v4 2/4] iotest 258: use script_main John Snow
2019-09-17  9:36   ` Vladimir Sementsov-Ogievskiy
2019-09-12  0:16 ` [Qemu-devel] [PATCH v4 3/4] iotests: specify protocol support via initialization info John Snow
2019-09-17  9:51   ` Vladimir Sementsov-Ogievskiy
2019-09-12  0:16 ` [Qemu-devel] [PATCH v4 4/4] iotests: use python logging for iotests.log() John Snow
2019-09-17 11:35   ` Vladimir Sementsov-Ogievskiy
2019-09-17 19:46     ` John Snow

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=59694b0e-b6c1-7dfb-818a-c82dc0f14947@redhat.com \
    --to=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=vsementsov@virtuozzo.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).