DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"Pattan, Reshma" <reshma.pattan@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/test: enhance sanity script
Date: Tue, 15 May 2018 18:17:28 +0200	[thread overview]
Message-ID: <117420816.XQrphXIzck@xps> (raw)
In-Reply-To: <7AE31235A30B41498D1C31348DC858BD5B3D4DED@IRSMSX103.ger.corp.intel.com>

15/05/2018 18:14, Parthasarathy, JananeeX M:
> From: Thomas Monjalon [mailto:thomas@monjalon.net] 
> > 10/05/2018 12:36, Jananee Parthasarathy:
> > > 1. Sanity Script is enhanced with additional test cases being added to
> > > autotest_data.py
> > 
> > How long they are?
> > How did you choose to group them?
> 
> It took approximately ~30 min, but longer duration is due to failed test cases (15m) which times out due to crash.

What was the duration of make test before your patch?

I think we need to keep a fast subset of tests.
Please check in mk/rte.sdktest.mk:
	PERFLIST=ring_perf,mempool_perf,memcpy_perf,hash_perf,timer_perf
	test-fast: BLACKLIST=-$(PERFLIST)

  reply	other threads:[~2018-05-15 16:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27 13:20 [dpdk-dev] [PATCH] " Reshma Pattan
2018-04-27 13:41 ` Burakov, Anatoly
2018-04-27 13:56 ` Burakov, Anatoly
2018-05-03 10:03   ` Parthasarathy, JananeeX M
2018-05-03 10:54     ` Burakov, Anatoly
2018-05-10 10:36 ` [dpdk-dev] [PATCH v2] " Jananee Parthasarathy
2018-05-13 22:12   ` Thomas Monjalon
2018-05-14 15:26     ` Pattan, Reshma
2018-05-14 15:29       ` Thomas Monjalon
2018-05-15 16:14     ` Parthasarathy, JananeeX M
2018-05-15 16:17       ` Thomas Monjalon [this message]
2018-05-18 13:32         ` Parthasarathy, JananeeX M
2018-05-18 13:48           ` Thomas Monjalon
2018-05-20 17:41             ` Parthasarathy, JananeeX M
2018-05-20 19:21               ` Thomas Monjalon
2018-05-15 15:58   ` [dpdk-dev] [PATCH v3 0/3] enhance sanity scripts Jananee Parthasarathy
2018-05-15 15:58     ` [dpdk-dev] [PATCH v3 1/3] app/test: add new test cases to sanity script Jananee Parthasarathy
2018-05-15 16:12       ` Burakov, Anatoly
2018-05-15 15:58     ` [dpdk-dev] [PATCH v3 2/3] app/test: update result for skipped test cases Jananee Parthasarathy
2018-05-15 15:58     ` [dpdk-dev] [PATCH v3 3/3] app/test: enhance freebsd support in sanity script Jananee Parthasarathy
2018-05-23 11:41     ` [dpdk-dev] [PATCH v4 0/4] enhance autotest config and test targets Jananee Parthasarathy
2018-05-23 11:41       ` [dpdk-dev] [PATCH v4 1/4] app/test: enhance autotest config Jananee Parthasarathy
2018-05-23 11:41       ` [dpdk-dev] [PATCH v4 2/4] app/test: update result for skipped test cases Jananee Parthasarathy
2018-05-23 11:41       ` [dpdk-dev] [PATCH v4 3/4] app/test: enhance freebsd support in autotest config Jananee Parthasarathy
2018-05-23 11:41       ` [dpdk-dev] [PATCH v4 4/4] mk: update make targets for classified testcases Jananee Parthasarathy

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=117420816.XQrphXIzck@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).