From: Cleber Rosa <crosa@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Make test
Date: Thu, 24 Aug 2017 18:16:57 -0400 [thread overview]
Message-ID: <89d8b7b1-fb0f-a967-927e-8795c7d2b324@redhat.com> (raw)
In-Reply-To: <9CE89958-B59C-4D3C-91C5-ECB4B153C43D@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
On 08/24/2017 05:50 PM, Programmingkid wrote:
>
> Thank you for the patches. I will test them. I was wondering what is the point to having both 'make check' and 'make test'. It looks like everyone is using 'make check'. Maybe we are better off removing the 'make test' target.
>
I think the removing the `make test` target is a good thing, if its
tests are either absorbed by an existing `make check*` one. Now that
depends on what people think the tcg tests (and others) deserve... TLC?
Total annihilation?
--
Cleber Rosa
[ Sr Software Engineer - Virtualization Team - Red Hat ]
[ Avocado Test Framework - avocado-framework.github.io ]
[ 7ABB 96EB 8B46 B94D 5E0F E9BB 657E 8D33 A5F2 09F3 ]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-24 22:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3749.1503600836.21955.qemu-devel@nongnu.org>
2017-08-24 19:10 ` [Qemu-devel] Make test Programmingkid
2017-08-24 20:41 ` Cleber Rosa
2017-08-24 21:50 ` Programmingkid
2017-08-24 22:16 ` Cleber Rosa [this message]
2017-08-25 5:49 ` Thomas Huth
2017-08-25 9:10 ` Peter Maydell
2017-08-25 9:33 ` Fam Zheng
2017-08-25 9:41 ` Peter Maydell
2017-08-24 22:18 ` Programmingkid
2017-08-24 22:21 ` Cleber Rosa
2017-08-24 22:24 ` Programmingkid
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=89d8b7b1-fb0f-a967-927e-8795c7d2b324@redhat.com \
--to=crosa@redhat.com \
--cc=programmingkidx@gmail.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).