All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [RFC 17.05] test: move tests to separate folder
Date: Wed, 15 Feb 2017 10:06:33 +0000	[thread overview]
Message-ID: <56b87137-6dd2-717c-b7bc-c55663c8c71f@intel.com> (raw)
In-Reply-To: <20170215021122.GW20916@yliu-dev.sh.intel.com>

On 2/15/2017 2:11 AM, Yuanhan Liu wrote:
> On Tue, Feb 14, 2017 at 05:30:14PM +0000, Richardson, Bruce wrote:
>> Just to be awkward :-), one last question: Why separate building and running
>> the tests? My suggestion would be to have "make test" both build and run the
>> tests. If there is no work to do in building them, then the time cost of the
>> extra empty build is negligible compared to the time taken to actually run
>> the tests.
> 
> +1
> 

Makes sense. I will update as:

"make test" -> compile and run test
"make test_build" -> only compile test

(newly added "make test_run" will go away)

thanks,
ferruh

> 	--yliu
> 
>> If we really want to build the tests without running them I'd
>> suggest "build_test" target instead. This keeps "make test" pretty much as
>> it was before.
>>
>> /Bruce

  reply	other threads:[~2017-02-15 10:06 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 15:13 [RFC 17.05] test: move tests to separate folder Ferruh Yigit
2017-02-14 15:41 ` Bruce Richardson
2017-02-14 15:51   ` Wiles, Keith
2017-02-14 16:12   ` Mcnamara, John
2017-02-15  9:03     ` Thomas Monjalon
2017-02-14 17:07   ` Ferruh Yigit
2017-02-14 17:30     ` Richardson, Bruce
2017-02-15  2:11       ` Yuanhan Liu
2017-02-15 10:06         ` Ferruh Yigit [this message]
2017-02-15 11:16           ` Thomas Monjalon
2017-02-15 11:28             ` Ferruh Yigit
2017-02-14 16:15 ` Mcnamara, John
2017-02-15 15:26 ` [PATCH 1/4] " Ferruh Yigit
2017-02-15 15:26   ` [PATCH 2/4] mk: do not build tests by default Ferruh Yigit
2017-02-15 16:58     ` Thomas Monjalon
2017-02-15 17:30       ` Ferruh Yigit
2017-02-16  8:53         ` Thomas Monjalon
2017-02-16 10:07           ` Ferruh Yigit
2017-02-15 15:26   ` [PATCH 3/4] mk: add new test-run make rule Ferruh Yigit
2017-02-15 17:07     ` Bruce Richardson
2017-02-15 17:41       ` Ferruh Yigit
2017-02-16  9:08         ` Bruce Richardson
2017-02-16  9:26     ` Thomas Monjalon
2017-02-16 10:21       ` Ferruh Yigit
2017-02-16 10:44         ` Thomas Monjalon
2017-02-15 15:26   ` [PATCH 4/4] mk: rename test related make rules Ferruh Yigit
2017-02-16  9:10   ` [PATCH 1/4] test: move tests to separate folder Bruce Richardson
2017-02-16 14:57   ` [PATCH v2 1/5] " Ferruh Yigit
2017-02-16 14:57     ` [PATCH v2 2/5] mk: do not build tests by default Ferruh Yigit
2017-02-16 14:57     ` [PATCH v2 3/5] mk: add new test-basic make rule Ferruh Yigit
2017-02-16 14:57     ` [PATCH v2 4/5] mk: rename test related make rules Ferruh Yigit
2017-02-16 14:57     ` [PATCH v2 5/5] doc: document test related make rules in make help Ferruh Yigit
2017-02-20 15:23       ` Mcnamara, John
2017-02-28 15:19     ` [PATCH v2 1/5] test: move tests to separate folder Thomas Monjalon

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=56b87137-6dd2-717c-b7bc-c55663c8c71f@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    --cc=yuanhan.liu@linux.intel.com \
    /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.