From: Luiz Capitulino <lcapitulino@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] First part of autoconfy series: cleanup tests/
Date: Fri, 22 Oct 2010 11:55:04 -0200 [thread overview]
Message-ID: <20101022115504.29636b79@doriath> (raw)
In-Reply-To: <4CC19763.6010501@redhat.com>
On Fri, 22 Oct 2010 15:53:39 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 10/22/2010 03:44 PM, Luiz Capitulino wrote:
> > > We could also have check-i386, check-qmp, etc. and check would simply
> > > call all of them.
> >
> > That would be perfect, I think. I mean, if we could stick only to check
> > to do all our unit-testing
>
> Well, the current "make test" is more integration testing than unit
> testing, so I'm not sure check can work for that. But autotest can,
> which is why I mentioned it.
Ah, got it.
next prev parent reply other threads:[~2010-10-22 13:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 8:18 [Qemu-devel] [PATCH 0/6] First part of autoconfy series: cleanup tests/ Paolo Bonzini
2010-10-21 8:18 ` [Qemu-devel] [PATCH 1/6] unbreak "make" from tests directory Paolo Bonzini
2010-10-21 8:18 ` [Qemu-devel] [PATCH 2/6] unbreak "make" from vpath-built " Paolo Bonzini
2010-10-21 8:18 ` [Qemu-devel] [PATCH 3/6] disable test_enter on i386, it is broken Paolo Bonzini
2010-10-21 8:18 ` [Qemu-devel] [PATCH 4/6] make runcom compile on recent distributions Paolo Bonzini
2010-10-21 8:18 ` [Qemu-devel] [PATCH 5/6] fix test_path Paolo Bonzini
2010-10-21 8:18 ` [Qemu-devel] [PATCH 6/6] rewrite i386 tests Makefile Paolo Bonzini
2010-10-22 13:26 ` [Qemu-devel] [PATCH 0/6] First part of autoconfy series: cleanup tests/ Luiz Capitulino
2010-10-22 13:38 ` Paolo Bonzini
2010-10-22 13:44 ` Luiz Capitulino
2010-10-22 13:53 ` Paolo Bonzini
2010-10-22 13:55 ` Luiz Capitulino [this message]
2010-10-23 14:54 ` Blue Swirl
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=20101022115504.29636b79@doriath \
--to=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--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).