All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Stefan Weil <sw@weilnetz.de>,
	Christoph Hellwig <hch@lst.de>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] qemu-iotest only for Linux?
Date: Thu, 15 Mar 2012 10:16:10 +0100	[thread overview]
Message-ID: <20120315091610.GA2070@lst.de> (raw)
In-Reply-To: <20120315075920.GA13870@stefanha-thinkpad.localdomain>

On Thu, Mar 15, 2012 at 07:59:20AM +0000, Stefan Hajnoczi wrote:
> On Wed, Mar 14, 2012 at 11:04:24PM +0100, Stefan Weil wrote:
> > What's the reason for "_supported_os Linux" in each test?
> > Because of this statement, the tests only run on Linux today,
> > although they could also run on BSD, w32 and other operating
> > systems (maybe small fixes are needed).
> > 
> > I don't think that adding every possible OS to each test
> > would be a good solution. Can we remove this OS dependency
> > completely?
> 
> In many cases the _supported_os was probably copy-pasted when creating
> new tests.  However, we can be pretty sure that the tests haven't all
> been run on anything other than Linux and maybe Windows recently.

Yes.

> I think we can support other host OSes but we should combine this with
> adding "make check" and maybe "make check-block" to the buildbot - that
> way we'll be notified if the tests break.  There are Linux, Solaris, and
> OpenBSD buildslaves.

For now please add the Oses it actually works as documentation, once
we have a good overview we can add classes like "generic" or "posix"

      reply	other threads:[~2012-03-15  9:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 22:04 [Qemu-devel] [RFC] qemu-iotest only for Linux? Stefan Weil
2012-03-15  7:59 ` Stefan Hajnoczi
2012-03-15  9:16   ` Christoph Hellwig [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=20120315091610.GA2070@lst.de \
    --to=hch@lst.de \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    --cc=sw@weilnetz.de \
    /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.