test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: "Tang, HaifengX" <haifengx.tang@intel.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: "Chen, WeichunX" <weichunx.chen@intel.com>
Subject: Re: [dts] dts support for executing case list in configuration file
Date: Tue, 14 Jul 2015 01:12:17 +0000	[thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10E60D28@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <DF029FFF923C334FAA58CEEB2979DCA6015735E7@SHSMSX103.ccr.corp.intel.com>

Haifeng,
If used cases name in configuration file will cause the configuration file too huge to manage.
And it also difficult to known that what cause the case not supported.

We plan to add check list for those cases which only supported in certain NIC.
I have talked about this topic with Huilong and Weichun, you can sync up with them.

From: Tang, HaifengX
Sent: Monday, July 13, 2015 5:39 PM
To: Liu, Yong; dts@dpdk.org
Cc: Tang, HaifengX
Subject: [dts] dts support for executing case list in configuration file

Hi all :

In dts  configuration file , one test suite represent several test cases . but in  these test cases  , some  of them are not supported different NICs  simultaneously .

So we want to put the case list that all  supported one NIC  in configuration file.  Does  Anyone  have some advices and suggestions about it ?

Example case list configuration file as below:

[Execution1]
crbs=xxx.xxx.xxx.xxx
drivername=igb_uio
test_cases=
      hello_world_all_cores,
hello_world_single_core,
cmdline_sample_commands,
[....]
   checksum_checking,
   packet_checking
targets=
    x86_64-native-linuxapp-gcc
parameters=nic_type=niantic:func=true

Thanks,
Haifeng

  reply	other threads:[~2015-07-14  1:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  9:39 Tang, HaifengX
2015-07-14  1:12 ` Liu, Yong [this message]
2015-07-14  1:28   ` Chen, WeichunX

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=86228AFD5BCD8E4EBFD2B90117B5E81E10E60D28@SHSMSX103.ccr.corp.intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=haifengx.tang@intel.com \
    --cc=weichunx.chen@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).