From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 8071C4F98 for ; Tue, 8 May 2018 08:45:29 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 May 2018 23:45:27 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,377,1520924400"; d="scan'208,217";a="53317227" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga001.fm.intel.com with ESMTP; 07 May 2018 23:45:26 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 7 May 2018 23:45:25 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.210]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.179]) with mapi id 14.03.0319.002; Tue, 8 May 2018 14:45:24 +0800 From: "Liu, Yong" To: "M R, Chengappa (Network Function Virtualization)" , "dts@dpdk.org" Thread-Topic: DPDK Test Suite: execution of full test cases Thread-Index: AdPixcb/GXnEpVtxRVuxpYmH9oR7SwAu/vwAAAHdoXAAwR0zAAACHhUg Date: Tue, 8 May 2018 06:45:24 +0000 Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E63037191@SHSMSX103.ccr.corp.intel.com> References: <86228AFD5BCD8E4EBFD2B90117B5E81E63033140@SHSMSX103.ccr.corp.intel.com> <86228AFD5BCD8E4EBFD2B90117B5E81E6303322F@SHSMSX103.ccr.corp.intel.com> In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMGQ2MjAyOTUtMTNiNi00NTM1LTk4ZDEtYmE0YWYwZDA4MWQwIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJpVUY1QmxJNWRLbDFwbXc0aXNHWlI4ZUhHb2lQVW5uSFBHZGRJMEs5TDgybHlaNlNVZEV0Z3prZElUN1UyRTVhIn0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [10.239.127.40] Content-Type: multipart/alternative; boundary="_000_86228AFD5BCD8E4EBFD2B90117B5E81E63037191SHSMSX103ccrcor_" MIME-Version: 1.0 Subject: Re: [dts] DPDK Test Suite: execution of full test cases X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2018 06:45:30 -0000 --_000_86228AFD5BCD8E4EBFD2B90117B5E81E63037191SHSMSX103ccrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Welcome Chengappa. According to the log file, look like DPDK can't build on your DUT. The fir= st error is that cc command can't be found. You need installed required packets for building. Reference link: http://dp= dk.org/doc/guides/linux_gsg/sys_reqs.html#compilation-of-the-dpdk Note: DTS will not setup DUT from brand new server. It only create or prepa= re the running environment for DPDK. DTS configurations look well, only one configuration need to be changed. = The reason is that DTS only distinguish FreeBSD and Linux OS distributions. os=3Dlinux Thanks, Marvin From: M R, Chengappa (Network Function Virtualization) [mailto:cm-r@hpe.com= ] Sent: Tuesday, May 08, 2018 2:13 PM To: Liu, Yong ; dts@dpdk.org Subject: RE: DPDK Test Suite: execution of full test cases Greetings Marvin, Thank you for welcoming me to DTS community - looking forward for some grea= t learnings here. I tried using the option of -debug -v and also did try to see the log files= - thank you for providing the pointers on the same. However, I am still blocked with compilation errors which I was encounterin= g earlier. What I see in the log files is as follows 08/05/2018 03:22:12 dut.10.70.2.6: export RTE_TARGET=3Dx86= _64-native-linuxapp-gcc 08/05/2018 03:22:12 dut.10.70.2.6: 08/05/2018 03:22:12 dut.10.70.2.6: export RTE_SDK=3D`pwd` 08/05/2018 03:22:12 dut.10.70.2.6: 08/05/2018 03:22:12 dut.10.70.2.6: rm -rf x86_64-native-li= nuxapp-gcc 08/05/2018 03:22:12 dut.10.70.2.6: 08/05/2018 03:22:12 dut.10.70.2.6: rm -rf ./app/test/test_= resource_c.res.o 08/05/2018 03:22:12 dut.10.70.2.6: 08/05/2018 03:22:12 dut.10.70.2.6: rm -rf ./app/test/test_= resource_tar.res.o 08/05/2018 03:22:12 dut.10.70.2.6: 08/05/2018 03:22:12 dut.10.70.2.6: rm -rf ./app/test/test_= pci_sysfs.res.o 08/05/2018 03:22:12 dut.10.70.2.6: 08/05/2018 03:22:12 dut.10.70.2.6: make -j 19 install T=3D= x86_64-native-linuxapp-gcc 08/05/2018 03:22:13 dut.10.70.2.6: /bin/sh: line 1: cc: co= mmand not found cat: /root/dpdk/x86_64-native-linuxapp-gcc/.config_tmp: No such file or dir= ectory Configuration done using x86_64-native-linuxapp-gcc /root/dpdk/mk/rte.vars.mk:56: *** RTE_ARCH is not defined. Stop. /root/dpdk/mk/rte.sdkroot.mk:100: recipe for target 'all' failed make[2]: *** [all] Error 2 /root/dpdk/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed make[1]: *** [pre_install] Error 2 /root/dpdk/mk/rte.sdkroot.mk:79: recipe for target 'install' failed make: *** [install] Error 2 08/05/2018 03:22:13 dut.10.70.2.6: make -j 19 -C test/ 08/05/2018 03:22:13 dut.10.70.2.6: make: Entering director= y '/root/dpdk/test' /root/dpdk/mk/rte.vars.mk:56: *** RTE_ARCH is not defined. Stop. make: Leaving directory '/root/dpdk/test' 08/05/2018 03:22:13 dut.10.70.2.6: cp -f ./test/test/test = ./x86_64-native-linuxapp-gcc/app 08/05/2018 03:22:13 dut.10.70.2.6: cp: cannot stat './test= /test/test': No such file or directory 08/05/2018 03:22:13 dut.10.70.2.6: cp -f ./test/test-acl/t= estacl ./x86_64-native-linuxapp-gcc/app 08/05/2018 03:22:13 dut.10.70.2.6: cp: cannot stat './test= /test-acl/testacl': No such file or directory 08/05/2018 03:22:13 dut.10.70.2.6: cp -f ./test/test-pipel= ine/testpipeline ./x86_64-native-linuxapp-gcc/app 08/05/2018 03:22:13 dut.10.70.2.6: cp: cannot stat './test= /test-pipeline/testpipeline': No such file or directory 08/05/2018 03:22:13 dut.10.70.2.6: cp -f ./test/cmdline_te= st/cmdline_test ./x86_64-native-linuxapp-gcc/app 08/05/2018 03:22:13 dut.10.70.2.6: cp: cannot stat './test= /cmdline_test/cmdline_test': No such file or directory 08/05/2018 03:22:13 dut.10.70.2.6: ERROR - try without '-j= ' 08/05/2018 03:22:13 dut.10.70.2.6: make install T=3Dx86_64= -native-linuxapp-gcc 08/05/2018 03:22:13 dut.10.70.2.6: /bin/sh: line 1: cc: co= mmand not found cat: /root/dpdk/x86_64-native-linuxapp-gcc/.config_tmp: No such file or dir= ectory Configuration done using x86_64-native-linuxapp-gcc /root/dpdk/mk/rte.vars.mk:56: *** RTE_ARCH is not defined. Stop. /root/dpdk/mk/rte.sdkroot.mk:100: recipe for target 'all' failed make[2]: *** [all] Error 2 /root/dpdk/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed make[1]: *** [pre_install] Error 2 /root/dpdk/mk/rte.sdkroot.mk:79: recipe for target 'install' failed make: *** [install] Error 2 08/05/2018 03:22:13 dut.10.70.2.6: make -j 19 -C test/ 08/05/2018 03:22:13 dut.10.70.2.6: make: Entering director= y '/root/dpdk/test' /root/dpdk/mk/rte.vars.mk:56: *** RTE_ARCH is not defined. Stop. make: Leaving directory '/root/dpdk/test' 08/05/2018 03:22:13 dut.10.70.2.6: cp -f ./test/test/test = ./x86_64-native-linuxapp-gcc/app 08/05/2018 03:22:13 dut.10.70.2.6: cp: cannot stat './test= /test/test': No such file or directory 08/05/2018 03:22:13 dut.10.70.2.6: cp -f ./test/test-acl/t= estacl ./x86_64-native-linuxapp-gcc/app 08/05/2018 03:22:14 dut.10.70.2.6: cp: cannot stat './test= /test-acl/testacl': No such file or directory 08/05/2018 03:22:14 dut.10.70.2.6: cp -f ./test/test-pipel= ine/testpipeline ./x86_64-native-linuxapp-gcc/app 08/05/2018 03:22:14 dut.10.70.2.6: cp: cannot stat './test= /test-pipeline/testpipeline': No such file or directory 08/05/2018 03:22:14 dut.10.70.2.6: cp -f ./test/cmdline_te= st/cmdline_test ./x86_64-native-linuxapp-gcc/app 08/05/2018 03:22:14 dut.10.70.2.6: cp: cannot stat './test= /cmdline_test/cmdline_test': No such file or directory 08/05/2018 03:22:14 dts: TARGET ERROR: Compilat= ion error... Could you kindly help me understand as to why I am facing this error - I un= derstand that once we have configured the TESTER will all the configuration= files and pre-requisites and have placed dpdk.tar.gz under /dep folder, TE= STER should configure the TARGET DUT with dpdk and should initiate the func= tional test cases. Kindly do let me know if am missing anything here. The configurations on my TESTER machine are as follows: [root@tester dts]# cat conf/ports.cfg # DUT Port Configuration # [DUT IP] # ports=3D # pci=3DPci BDF,intf=3DKernel interface; # pci=3DPci BDF,mac=3DMac address,peer=3DTester Pci BDF,numa=3DPort Num= a # pci=3DPci BDF,peer=3DIXIA:card.port # pci=3DPci BDF,peer=3DTester Pci BDF,tp_ip=3D$(IP),tp_path=3D$({PERL_P= ATH); # pci=3DPci BDF,peer=3DTester Pci BDF,sec_port=3Dyes,first_port=3DPci B= DF; # [VM NAME] virtual machine name; This section is for virutal scenario # ports =3D # dev_idx=3Ddevice index of ports info, peer=3DTester Pci BDF [10.70.2.6] ports =3D pci=3D05:00.0,intf=3Dens2f0; pci=3D05:00.1,intf=3Dens2f1; [root@tester dts]# cat executions/execution.cfg [Execution1] crbs=3D10.70.2.6 drivername=3Digb_uio test_suites=3Dhello_world test_suites=3D cmdline, hello_world targets=3Dx86_64-native-linuxapp-gcc parameters=3Dnic_type=3Dniantic:func=3Dtrue [root@tester dts]# cat conf/crbs.cfg #DUT crbs Configuration #[DUT IP] # dut_ip: DUT ip address # dut_user: Login DUT username # dut_passwd: Login DUT password # os: operation system type linux or freebsd # tester_ip: Tester ip address # tester_passwd: Tester password # ixia_group: IXIA group name # channels: Board channel number # bypass_core0: Whether by pass core0 [10.70.2.6] dut_ip=3D10.70.2.6 dut_user=3Droot dut_passwd=3DHP1nvent os=3Dfedora tester_ip=3D10.70.2.5 tester_passwd=3DHP1nvent channels=3D4 Thanking in advance, Chengappa From: Liu, Yong [mailto:yong.liu@intel.com] Sent: Friday, May 04, 2018 2:52 PM To: Liu, Yong >; M R, Chengap= pa (Network Function Virtualization) >; d= ts@dpdk.org Subject: RE: DPDK Test Suite: execution of full test cases Chengappa, You can also utilize verbose and debug option for DTS issue debugging. Command will like: ./dts --debug -v Thanks, Marvin From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Liu, Yong Sent: Friday, May 04, 2018 4:33 PM To: M R, Chengappa (Network Function Virtualization) >; dts@dpdk.org Subject: Re: [dts] DPDK Test Suite: execution of full test cases Hi Chengappa, Welcome to DTS community. The detail running log of DTS will located at output/dts.log. You can check= the error when building dpdk in the log file. DTS master branch now supporting dpdk v18.02. If you are testing other vers= ions of DPDK, you may need to switch DTS version. DTS tutorial is at http://dpdk.org/doc/dts/gsg/tutorial.html. You can refer= ence to it. Thanks, Marvin From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of M R, Chengappa (Networ= k Function Virtualization) Sent: Thursday, May 03, 2018 6:19 PM To: dts@dpdk.org Subject: [dts] DPDK Test Suite: execution of full test cases Hello Team, Greetings! We are aiming to install DTS and execute the test cases which are part of D= TS framework. However, we are frequently facing issues and currently failing to execute t= he test cases. Currently we are blocked as we are encountering the issue which is describe= r here - http://dpdk.org/ml/archives/dts/2018-May/003990.html Am initiating this thread to check - 1. Is there any logging options enabled with DTS so that we could see t= he log traces 2. Also need to understand if anyone here in this community who has exe= rcised end-to-end DPDK test suite with all the test cases - if so would lik= e to understand what is the running configuration on TESTER and TARGET DUT Thanking in advance, Chengappa --_000_86228AFD5BCD8E4EBFD2B90117B5E81E63037191SHSMSX103ccrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Welcome Chengappa.

 

According to the log f= ile, look like DPDK can’t build on your DUT.  The first error is= that cc command can’t be found.

You need installed req= uired packets for building. Reference link: http://dpdk.org/doc/guides/linux_gsg/sys_reqs.html#compilation-of-the-dpdk<= /a>

 

Note: DTS will not set= up DUT from brand new server. It only create or prepare the running environ= ment for DPDK.

 

DTS configurations loo= k well,  only one configuration need to be changed.  The reason i= s that DTS only distinguish FreeBSD and Linux OS distributions.

os=3Dlinux

 

Thanks,

Marvin

 

From: M R= , Chengappa (Network Function Virtualization) [mailto:cm-r@hpe.com]
Sent: Tuesday, May 08, 2018 2:13 PM
To: Liu, Yong <yong.liu@intel.com>; dts@dpdk.org
Subject: RE: DPDK Test Suite: execution of full test cases

 

Greetings Marvin,

 

Thank you for welcoming me to DTS communit= y – looking forward for some great learnings here.<= /p>

 

I tried using the option of –debug &= #8211;v and also did try to see the log files – thank you for providi= ng the pointers on the same.

 

However, I am still blocked with compilati= on errors which I was encountering earlier.

 

What I see in the log files is as follows

 

 

08/05/2018 03:22:12         =          dut.10.70.2.6: export RTE_= TARGET=3Dx86_64-native-linuxapp-gcc

08/05/2018 03:22:12         =          dut.10.70.2.6:<= /span>

08/05/2018 03:22:12         =          dut.10.70.2.6: export RTE_= SDK=3D`pwd`

08/05/2018 03:22:12         =          dut.10.70.2.6:<= /span>

08/05/2018 03:22:12         =          dut.10.70.2.6: rm -rf x86_= 64-native-linuxapp-gcc

08/05/2018 03:22:12         =          dut.10.70.2.6:<= /span>

08/05/2018 03:22:12         =          dut.10.70.2.6: rm -rf ./ap= p/test/test_resource_c.res.o

08/05/2018 03:22:12         =          dut.10.70.2.6:<= /span>

08/05/2018 03:22:12         =          dut.10.70.2.6: rm -rf ./ap= p/test/test_resource_tar.res.o

08/05/2018 03:22:12         =          dut.10.70.2.6:<= /span>

08/05/2018 03:22:12         =          dut.10.70.2.6: rm -rf ./ap= p/test/test_pci_sysfs.res.o

08/05/2018 03:22:12         =          dut.10.70.2.6:<= /span>

08/05/2018 03:22:12         =          dut.10.70.2.6: make -j 19 = install T=3Dx86_64-native-linuxapp-gcc

08/05/2018 03:22:13         =          dut.10.70.2.6: /bin/sh: li= ne 1: cc: command not found

cat: /root/dpdk/x86_64-native-linuxapp-gcc/.config_tmp: No such file or d= irectory

Configuration done using x86_64-native-linuxapp-gcc

/root/dpdk/mk/rte.vars.mk:56: *** RTE_ARCH is not defined.  Stop.

/root/dpdk/mk/rte.sdkroot.mk:100: recipe for target 'all' failed

make[2]: *** [all] Error 2

/root/dpdk/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' faile= d

make[1]: *** [pre_install] Error 2

/root/dpdk/mk/rte.sdkroot.mk:79: recipe for target 'install' failed<= /o:p>

make: *** [install] Error 2

08/05/2018 03:22:13          = ;        dut.10.70.2.6: make -j 19 = -C test/

08/05/2018 03:22:13         =          dut.10.70.2.6: make: Enter= ing directory '/root/dpdk/test'

/root/dpdk/mk/rte.vars.mk:56: *** RTE_ARCH is not defined.  Stop.

make: Leaving directory '/root/dpdk/test'

08/05/2018 03:22:13         =          dut.10.70.2.6: cp -f ./tes= t/test/test ./x86_64-native-linuxapp-gcc/app

08/05/2018 03:22:13         =          dut.10.70.2.6: cp: cannot = stat ‘./test/test/test’: No such file or directory

08/05/2018 03:22:13         =          dut.10.70.2.6: cp -f ./tes= t/test-acl/testacl ./x86_64-native-linuxapp-gcc/app

08/05/2018 03:22:13         =          dut.10.70.2.6: cp: cannot = stat ‘./test/test-acl/testacl’: No such file or directory<= /o:p>

08/05/2018 03:22:13         =          dut.10.70.2.6: cp -f ./tes= t/test-pipeline/testpipeline ./x86_64-native-linuxapp-gcc/app

08/05/2018 03:22:13         =          dut.10.70.2.6: cp: cannot = stat ‘./test/test-pipeline/testpipeline’: No such file or direc= tory

08/05/2018 03:22:13         =          dut.10.70.2.6: cp -f ./tes= t/cmdline_test/cmdline_test ./x86_64-native-linuxapp-gcc/app

08/05/2018 03:22:13         =          dut.10.70.2.6: cp: cannot = stat ‘./test/cmdline_test/cmdline_test’: No such file or direct= ory

08/05/2018 03:22:13       = ;           dut.10.70.2.6= : ERROR - try without '-j'

08/05/2018 03:22:13         =          dut.10.70.2.6: make instal= l T=3Dx86_64-native-linuxapp-gcc

08/05/2018 03:22:13         =          dut.10.70.2.6: /bin/sh: li= ne 1: cc: command not found

cat: /root/dpdk/x86_64-native-linuxapp-gcc/.config_tmp: No such file or d= irectory

Configuration done using x86_64-native-linuxapp-gcc

/root/dpdk/mk/rte.vars.mk:56: *** RTE_ARCH is not defined.  Stop.

/root/dpdk/mk/rte.sdkroot.mk:100: recipe for target 'all' failed

make[2]: *** [all] Error 2

/root/dpdk/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' faile= d

make[1]: *** [pre_install] Error 2

/root/dpdk/mk/rte.sdkroot.mk:79: recipe for target 'install' failed<= /o:p>

make: *** [install] Error 2

08/05/2018 03:22:13         =          dut.10.70.2.6: make -j 19 = -C test/

08/05/2018 03:22:13         =          dut.10.70.2.6: make: Enter= ing directory '/root/dpdk/test'

/root/dpdk/mk/rte.vars.mk:56: *** RTE_ARCH is not defined.  Stop.

make: Leaving directory '/root/dpdk/test'

08/05/2018 03:22:13         =          dut.10.70.2.6: cp -f ./tes= t/test/test ./x86_64-native-linuxapp-gcc/app

08/05/2018 03:22:13         =          dut.10.70.2.6: cp: cannot = stat ‘./test/test/test’: No such file or directory

08/05/2018 03:22:13         =         dut.10.70.2.6: cp -f ./tes= t/test-acl/testacl ./x86_64-native-linuxapp-gcc/app

08/05/2018 03:22:14         =          dut.10.70.2.6: cp: cannot = stat ‘./test/test-acl/testacl’: No such file or directory<= /o:p>

08/05/2018 03:22:14         =          dut.10.70.2.6: cp -f ./tes= t/test-pipeline/testpipeline ./x86_64-native-linuxapp-gcc/app

08/05/2018 03:22:14         =          dut.10.70.2.6: cp: cannot = stat ‘./test/test-pipeline/testpipeline’: No such file or direc= tory

08/05/2018 03:22:14         =          dut.10.70.2.6: cp -f ./tes= t/cmdline_test/cmdline_test ./x86_64-native-linuxapp-gcc/app

08/05/2018 03:22:14         =          dut.10.70.2.6: cp: cannot = stat ‘./test/cmdline_test/cmdline_test’: No such file or direct= ory

08/05/2018 03:22:14       = ;            &n= bsp;        dts:  TARGET ERROR: Com= pilation error...

 

Could you kindly help me understand as to = why I am facing this error – I understand that once we have configure= d the TESTER will all the configuration files and pre-requisites and have placed dpdk.tar.gz under /dep folder, TESTER should configure the= TARGET DUT with dpdk and should initiate the functional test cases.

 

Kindly do let me know if am missing anythi= ng here.

 

The configurations on my TESTER machine ar= e as follows:

 

[root@tester dts]# cat conf/ports.cfg

# DUT Port Configuration

# [DUT IP]

# ports=3D

#     pci=3DPci BDF,intf=3DKernel interface;

#     pci=3DPci BDF,mac=3DMac address,peer=3DTester P= ci BDF,numa=3DPort Numa

#     pci=3DPci BDF,peer=3DIXIA:card.port<= /span>

#     pci=3DPci BDF,peer=3DTester Pci BDF,tp_ip=3D$(I= P),tp_path=3D$({PERL_PATH);

#     pci=3DPci BDF,peer=3DTester Pci BDF,sec_port=3D= yes,first_port=3DPci BDF;

# [VM NAME] virtual machine name; This section is for virutal scenario

# ports =3D

#     dev_idx=3Ddevice index of ports info, peer=3DTe= ster Pci BDF

[10.70.2.6]

ports =3D

    pci=3D05:00.0,intf=3Dens2f0;

    pci=3D05:00.1,intf=3Dens2f1;

 

 

[root@tester dts]# cat executions/execution.cfg<= /p>

[Execution1]

crbs=3D10.70.2.6

drivername=3Digb_uio

test_suites=3Dhello_world

test_suites=3D

    cmdline,

    hello_world

targets=3Dx86_64-native-linuxapp-gcc

parameters=3Dnic_type=3Dniantic:func=3Dtrue

 

 

[root@tester dts]# cat conf/crbs.cfg

#DUT crbs Configuration

#[DUT IP]

#  dut_ip: DUT ip address

#  dut_user: Login DUT username

#  dut_passwd: Login DUT password

#  os: operation system type linux or freebsd

#  tester_ip: Tester ip address

#  tester_passwd: Tester password

#  ixia_group: IXIA group name

#  channels: Board channel number

#  bypass_core0: Whether by pass core0

[10.70.2.6]

dut_ip=3D10.70.2.6

dut_user=3Droot

dut_passwd=3DHP1nvent

os=3Dfedora

tester_ip=3D10.70.2.5

tester_passwd=3DHP1nvent

channels=3D4

 

 

Thanking in advance,

Chengappa

 

From: Liu, Yong [mailto:yong.liu@intel.com]
Sent: Friday, May 04, 2018 2:52 PM
To: Liu, Yong <yong.liu@int= el.com>; M R, Chengappa (Network Function Virtualization) <cm-r@hpe.com>; dts@dpdk.org
Subject: RE: DPDK Test Suite: execution of full test cases

 

Chengappa,<= /span>

You can also utilize v= erbose and debug option for DTS issue debugging.

Command will like:

./dts --debug –v

 

Thanks,

Marvin

 

From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Liu, Yong
Sent: Friday, May 04, 2018 4:33 PM
To: M R, Chengappa (Network Function Virtualization) <cm-r@hpe.com>; dts@dpdk.org
Subject: Re: [dts] DPDK Test Suite: execution of full test cases

 

Hi Chengappa,

Welcome to DTS communi= ty.

The detail running log= of DTS will located at output/dts.log. You can check the error when buildi= ng dpdk in the log file.

DTS master branch now = supporting dpdk v18.02. If you are testing other versions of DPDK, you may = need to switch DTS version.

 

DTS tutorial is at http://dpdk.org/doc/dts/gsg/tutorial.html. You can reference to it.

 

Thanks,
Marvin

 

From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of M R, Chengappa (Network Function Virtualization)
Sent: Thursday, May 03, 2018 6:19 PM
To: dts@dpdk.org
Subject: [dts] DPDK Test Suite: execution of full test cases

 

Hello Team,

Greetings!

 

We are aiming to install DTS and execute t= he test cases which are part of DTS framework.

 

However, we are frequently facing issues a= nd currently failing to execute the test cases.

 

Currently we are blocked as we are encount= ering the issue which is describer here –

http://dpdk.org/ml/archives/dts/2018-May/003990.html=

 

Am initiating this thread to check –=

 

1.   &nbs= p; Is there any logging options enabl= ed with DTS so that we could see the log traces

 

2.   &nbs= p; Also need to understand if anyone = here in this community who has exercised end-to-end DPDK test suite with al= l the test cases – if so would like to understand what is the running configuration on TESTER and TARGET DUT

 

 

Thanking in advance,

Chengappa

--_000_86228AFD5BCD8E4EBFD2B90117B5E81E63037191SHSMSX103ccrcor_--