All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Programmingkid <programmingkidx@gmail.com>,
	Riku Voipio <riku.voipio@iki.fi>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] make test fails on Mac OS X
Date: Sat, 11 Apr 2015 22:31:42 +0100	[thread overview]
Message-ID: <CAFEAcA_M2KDP5Gs64WtBO=8r_VF_FB1jgnnLrRLOA8EhMqrNMw@mail.gmail.com> (raw)
In-Reply-To: <55298349.2030308@suse.de>

On 11 April 2015 at 21:25, Andreas Färber <afaerber@suse.de> wrote:
> Similar in spirit to some of those tests, I had been thinking about
> testing linux-user by running host binaries, comparing native and
> emulated output. make check only covers the softmmus today.

Yeah. I run the linux-user-test binaries from http://wiki.qemu.org/Testing
as a smoke-test that we haven't totally broken things. I think
Riku has a more comprehensive set of tests. There's also the
LTP linux-test-project tests, though those are pretty heavyweight.

The thing I usually end up getting stuck on with linux-user
tests is how you make this (a) runnable by anybody (b) reproducible
(c) gpl-compliant where relevant (d) easy for anybody to update
the tests. The first and arguably the second of those requires
"doesn't need a target toolchain when running 'make check'", but
the second two argue for "don't check binary blobs into git"...

-- PMM

      reply	other threads:[~2015-04-11 21:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 17:56 [Qemu-devel] make test fails on Mac OS X Programmingkid
2015-04-10 21:37 ` Peter Maydell
2015-04-11 15:46 ` Andreas Färber
2015-04-11 15:52   ` Peter Maydell
2015-04-11 20:25     ` Andreas Färber
2015-04-11 21:31       ` Peter Maydell [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='CAFEAcA_M2KDP5Gs64WtBO=8r_VF_FB1jgnnLrRLOA8EhMqrNMw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=afaerber@suse.de \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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.