qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Cleber Rosa <crosa@redhat.com>,
	Programmingkid <programmingkidx@gmail.com>
Cc: qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] Make test
Date: Fri, 25 Aug 2017 07:49:08 +0200	[thread overview]
Message-ID: <1adde8d7-762f-8e89-7192-32d370b72af6@redhat.com> (raw)
In-Reply-To: <89d8b7b1-fb0f-a967-927e-8795c7d2b324@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

On 25.08.2017 00:16, Cleber Rosa wrote:
> 
> 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?

Since we do not have very good test coverage for TCG yet, I'd like to
see this rather fixed than removed! Could you please CC: me on future
versions of your patch series (I missed v1)?

And I'd suggest to rename "make test" to "make check-tcg" to align it
with the other check* targets. (I remember the very first time I was
trying to run the QEMU tests and this "check" vs. "test" naming caused
really some confusion for me).

 Thomas


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2017-08-25  5:49 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
2017-08-25  5:49         ` Thomas Huth [this message]
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=1adde8d7-762f-8e89-7192-32d370b72af6@redhat.com \
    --to=thuth@redhat.com \
    --cc=crosa@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).