From: "Kantecki, Tomasz" <tomasz.kantecki@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] fast red autotest
Date: Fri, 27 May 2016 14:04:23 +0000 [thread overview]
Message-ID: <E79CF84CF47B0B42B66F4F5835125F9C81824FE1@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <17438858.1XjK0Grm1a@xps13>
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> 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.
It sounds like a good idea Thomas. I ran the test couple of times and it seems that functional test #4 takes most of the time and could be removed to long run scenario. Other functional tests run rather promptly.
Next week, I can prepare patch to implement long and short run commands for this test suite. Would it be OK?
Tomasz
--------------------------------------------------------------
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
next prev parent reply other threads:[~2016-05-27 14:04 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
2016-05-27 14:04 ` Kantecki, Tomasz [this message]
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=E79CF84CF47B0B42B66F4F5835125F9C81824FE1@IRSMSX101.ger.corp.intel.com \
--to=tomasz.kantecki@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).