From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Kantecki, Tomasz" <tomasz.kantecki@intel.com>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] fast red autotest
Date: Wed, 25 May 2016 13:41:03 +0200 [thread overview]
Message-ID: <17438858.1XjK0Grm1a@xps13> (raw)
In-Reply-To: <E79CF84CF47B0B42B66F4F5835125F9C8181AECF@IRSMSX101.ger.corp.intel.com>
2016-05-25 11:06, Kantecki, Tomasz:
> I had a quick look through these tests and it will need some effort to rework them to run in shorter time.
> I agree to remove this suite from the fast_test as long as it gets exercised in other test paths.
Is it possible to split them in
- short functional tests
- long run / perf tests
?
So we could keep some basic tests in fast_test.
I expect that tests which are not part of fast_test won't be run often
or in enough various environments.
next prev parent reply other threads:[~2016-05-25 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 7:45 Thomas Monjalon
2016-05-11 10:15 ` Dumitrescu, Cristian
2016-05-24 15:23 ` Thomas Monjalon
2016-05-24 17:08 ` Dumitrescu, Cristian
2016-05-25 11:06 ` Kantecki, Tomasz
2016-05-25 11:41 ` Thomas Monjalon [this message]
2016-05-27 14:04 ` Kantecki, Tomasz
2016-05-27 14:42 ` 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=17438858.1XjK0Grm1a@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=tomasz.kantecki@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).