DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Reshma Pattan <reshma.pattan@intel.com>,
	anatoly.burakov@intel.com, jananeex.m.parthasarathy@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v6 00/10] Make unit tests great again
Date: Tue, 31 Jul 2018 16:41:16 +0200	[thread overview]
Message-ID: <5476000.D8aPes4ZpC@xps> (raw)
In-Reply-To: <1532684420-29500-1-git-send-email-reshma.pattan@intel.com>

27/07/2018 11:40, Reshma Pattan:
> Previously, unit tests were running in groups. There were technical
> reasons why that was the case (mostly having to do with limiting memory),
> but it was hard to maintain and update the autotest script.
> In 18.05, limiting of memory at DPDK startup was no longer necessary,
> as DPDK allocates memory at runtime as needed. This has the implication
> that the old test grouping can now be retired and replaced with a more
> sensible way of running unit tests (using multiprocessing pool of workers
> and a queue of tests). This patchset accomplishes exactly that.
> 
> This patchset merges changes done in [1], [2]
> 
> [1] http://dpdk.org/dev/patchwork/patch/40370/
> [2] http://patches.dpdk.org/patch/40373/
> 
> Removed unused and duplicate make rules for test-basic, 
> test-mempool, test-ring from make file system in patch 10/10.
> 
> v5: Corrected the patch Authorship.
> 
> 
> Anatoly Burakov (7):
>   autotest: fix printing
>   autotest: fix invalid code on reports
>   autotest: make autotest runner python 2/3 compliant
>   autotest: visually separate different test categories
>   autotest: improve filtering
>   autotest: remove autotest grouping
>   autotest: properly parallelize unit tests
> 
> Jananee Parthasarathy (2):
>   autotest: update autotest test case list
>   mk: update make targets for classified testcases
> 
> Reshma Pattan (1):
>   mk: remove unnecessary make rules of test

Applied, thanks

      parent reply	other threads:[~2018-07-31 14:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27  9:40 Reshma Pattan
2018-07-27  9:40 ` [dpdk-dev] [PATCH v6 01/10] autotest: fix printing Reshma Pattan
2018-07-27  9:40 ` [dpdk-dev] [PATCH v6 02/10] autotest: fix invalid code on reports Reshma Pattan
2018-07-27  9:40 ` [dpdk-dev] [PATCH v6 03/10] autotest: make autotest runner python 2/3 compliant Reshma Pattan
2018-07-27  9:40 ` [dpdk-dev] [PATCH v6 04/10] autotest: visually separate different test categories Reshma Pattan
2018-07-27  9:40 ` [dpdk-dev] [PATCH v6 05/10] autotest: improve filtering Reshma Pattan
2018-07-27  9:40 ` [dpdk-dev] [PATCH v6 06/10] autotest: remove autotest grouping Reshma Pattan
2018-07-27  9:40 ` [dpdk-dev] [PATCH v6 07/10] autotest: properly parallelize unit tests Reshma Pattan
2018-07-27  9:40 ` [dpdk-dev] [PATCH v6 08/10] autotest: update autotest test case list Reshma Pattan
2018-07-27  9:40 ` [dpdk-dev] [PATCH v6 09/10] mk: update make targets for classified testcases Reshma Pattan
2018-07-27  9:40 ` [dpdk-dev] [PATCH v6 10/10] mk: remove unnecessary make rules of test Reshma Pattan
2018-07-31 14:41 ` Thomas Monjalon [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=5476000.D8aPes4ZpC@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=jananeex.m.parthasarathy@intel.com \
    --cc=reshma.pattan@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 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).