From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from g4t3426.houston.hpe.com (g4t3426.houston.hpe.com [15.241.140.75]) by dpdk.org (Postfix) with ESMTP id 1F7D23977 for ; Tue, 8 May 2018 08:13:18 +0200 (CEST) Received: from G9W8453.americas.hpqcorp.net (g9w8453.houston.hp.com [16.216.160.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by g4t3426.houston.hpe.com (Postfix) with ESMTPS id 121B24E for ; Tue, 8 May 2018 06:13:18 +0000 (UTC) Received: from G4W9119.americas.hpqcorp.net (2002:10d2:14d6::10d2:14d6) by G9W8453.americas.hpqcorp.net (2002:10d8:a0d3::10d8:a0d3) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 8 May 2018 06:13:17 +0000 Received: from NAM03-BY2-obe.outbound.protection.outlook.com (15.241.52.12) by G4W9119.americas.hpqcorp.net (16.210.20.214) with Microsoft SMTP Server (TLS) id 15.0.1178.4 via Frontend Transport; Tue, 8 May 2018 06:13:17 +0000 Received: from TU4PR8401MB0654.NAMPRD84.PROD.OUTLOOK.COM (10.169.44.148) by TU4PR8401MB0333.NAMPRD84.PROD.OUTLOOK.COM (10.169.42.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.735.18; Tue, 8 May 2018 06:13:14 +0000 Received: from TU4PR8401MB0654.NAMPRD84.PROD.OUTLOOK.COM ([fe80::6839:52c0:9d6f:a517]) by TU4PR8401MB0654.NAMPRD84.PROD.OUTLOOK.COM ([fe80::6839:52c0:9d6f:a517%17]) with mapi id 15.20.0735.019; Tue, 8 May 2018 06:13:14 +0000 From: "M R, Chengappa (Network Function Virtualization)" To: "Liu, Yong" , "dts@dpdk.org" Thread-Topic: DPDK Test Suite: execution of full test cases Thread-Index: AdPixcb/GXnEpVtxRVuxpYmH9oR7SwAu/vwAAAHdoXAAwR0zAA== Date: Tue, 8 May 2018 06:13:14 +0000 Message-ID: References: <86228AFD5BCD8E4EBFD2B90117B5E81E63033140@SHSMSX103.ccr.corp.intel.com> <86228AFD5BCD8E4EBFD2B90117B5E81E6303322F@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <86228AFD5BCD8E4EBFD2B90117B5E81E6303322F@SHSMSX103.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=cm-r@hpe.com; x-originating-ip: [16.242.235.132] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; TU4PR8401MB0333; 7:vsWtzSVKK6LjSkmaNa5JVXW9h4h40m1O8+UU2P35ZN2mpSo+r0RMW+ioTKz6Gig9CTgwgVJIUWzK5/o4GhArLjd42o3ZWrfTSowflXfKLbjXSFFqR7e4SC0rSkCFlXF2g/F7iuiqhv8IV7URQp45gM3PDTi7PKIXbrzPnkuix/aMGGSVlFznqCfw/vxFypEDLT/iwe9ZNDspomOL6fyEHjKxdyrpB7UW8z1xabde1SxYhlzgjazQ5E1YZgDHdrP7 x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:(222181515654134); BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989080)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(48565401081)(2017052603328)(7153060)(7193020); SRVR:TU4PR8401MB0333; x-ms-traffictypediagnostic: TU4PR8401MB0333: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(28532068793085)(227479698468861)(21748063052155)(222181515654134)(228905959029699); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(3231254)(944501410)(52105095)(93006095)(93001095)(10201501046)(6055026)(149027)(150027)(6041310)(20161123558120)(20161123564045)(20161123562045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:TU4PR8401MB0333; BCL:0; PCL:0; RULEID:; SRVR:TU4PR8401MB0333; x-forefront-prvs: 0666E15D35 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(39380400002)(346002)(366004)(39860400002)(396003)(189003)(199004)(229853002)(3280700002)(2900100001)(966005)(2906002)(21615005)(81156014)(3660700001)(8676002)(2501003)(97736004)(6246003)(81166006)(6116002)(7736002)(86362001)(486006)(14454004)(3846002)(106356001)(790700001)(53376002)(5660300001)(476003)(74316002)(478600001)(110136005)(9686003)(11346002)(236005)(68736007)(33656002)(76176011)(186003)(99286004)(5250100002)(6306002)(6436002)(345774005)(8936002)(54896002)(53546011)(55016002)(53946003)(26005)(7696005)(102836004)(105586002)(19273905006)(6506007)(606006)(59450400001)(551544002)(316002)(66066001)(25786009)(53936002)(446003); DIR:OUT; SFP:1102; SCL:1; SRVR:TU4PR8401MB0333; H:TU4PR8401MB0654.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: hpe.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: 1TLlrzDtmwS91w982OIY9XH/Abch5Mx+tnA/Ne+Ku4CUdfbyF6rUg7VDiMODCEqlzHmbEfdPoA2Jcd/N2uLJxgL58wOCkOyzkdJU6u3gkXlr0vM4ARWPRWV6+Pvpp6AhJ9NAppe4SQzk2nMB1f0Czv5fqx9wImNBfU/NHoNNfvPiXSOC8gX/+PT/cLftWz4e spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_TU4PR8401MB0654818B5100AC829E03CF9D999A0TU4PR8401MB0654_" MIME-Version: 1.0 X-MS-Office365-Filtering-Correlation-Id: 422f828c-6b5c-4252-68d0-08d5b4aac8d5 X-MS-Exchange-CrossTenant-Network-Message-Id: 422f828c-6b5c-4252-68d0-08d5b4aac8d5 X-MS-Exchange-CrossTenant-originalarrivaltime: 08 May 2018 06:13:14.8521 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc X-MS-Exchange-Transport-CrossTenantHeadersStamped: TU4PR8401MB0333 X-OriginatorOrg: hpe.com 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:13:19 -0000 --_000_TU4PR8401MB0654818B5100AC829E03CF9D999A0TU4PR8401MB0654_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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, Chengappa (Network Function Virtua= lization) ; dts@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 = the log traces 2. Also need to understand if anyone here in this community who has ex= ercised end-to-end DPDK test suite with all the test cases - if so would li= ke to understand what is the running configuration on TESTER and TARGET DUT Thanking in advance, Chengappa --_000_TU4PR8401MB0654818B5100AC829E03CF9D999A0TU4PR8401MB0654_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings Marvin,

 

Thank you for welcoming me to D= TS community – looking forward for some great learnings here.

 

I tried using the option of = 211;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 wit= h compilation 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 unders= tand as to why I am facing this error – I understand that once we hav= e configured the TESTER will all the configuration files and pre-requisites and have placed dpdk.tar.gz under /dep folder, TESTER s= hould configure the TARGET DUT with dpdk and should initiate the functional= test cases.

 

Kindly do let me know if am mis= sing 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 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] <= br> Sent: Friday, May 04, 2018 2:52 PM
To: Liu, Yong <yong.liu@intel.com>; M R, Chengappa (Network Fu= nction 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 an= d execute the test cases which are part of DTS framework.=

 

However, we are frequently faci= ng issues and currently failing to execute the test cases.

 

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

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

 

Am initiating this thread to ch= eck –

 

1.  = ;    Is there any logging op= tions enabled with DTS so that we could see the log traces

 =

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

 =

 

Thanking in advance,=

Chengappa

--_000_TU4PR8401MB0654818B5100AC829E03CF9D999A0TU4PR8401MB0654_--