<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="#0563C1" vlink="#954F72"> <div class="WordSection1"> Welcome Chengappa. <o:p></o:p> <o:p> </o:p> According to the log file, look like DPDK can’t build on your DUT. The first error is that cc command can’t be found. <o:p></o:p> You need installed required packets for building. Reference link: <a href="http://dpdk.org/doc/guides/linux_gsg/sys_reqs.html#compilation-of-the-dpdk"> http://dpdk.org/doc/guides/linux_gsg/sys_reqs.html#compilation-of-the-dpdk</a><o:p></o:p> <o:p> </o:p> Note: DTS will not setup DUT from brand new server. It only create or prepare the running environment for DPDK. <o:p></o:p> <o:p> </o:p> DTS configurations look well, only one configuration need to be changed. The reason is that DTS only distinguish FreeBSD and Linux OS distributions. <o:p></o:p> os=linux<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> Marvin<o:p></o:p> <o:p> </o:p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> <a name="_____replyseparator"></a>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<o:p></o:p> </div> </div> <o:p> </o:p> Greetings Marvin,<o:p></o:p> <o:p> </o:p> Thank you for welcoming me to DTS community – looking forward for some great learnings here.<o:p></o:p> <o:p> </o:p> 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.<o:p></o:p> <o:p> </o:p> However, I am still blocked with compilation errors which I was encountering earlier.<o:p></o:p> <o:p> </o:p> What I see in the log files is as follows <o:p></o:p> <o:p> </o:p> <o:p> </o:p> <table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="background:#FBE4D5;border-collapse:collapse"> <tbody> <tr> <td width="559" valign="top" style="width:899.6pt;border:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt"> 08/05/2018 03:22:12 dut.10.70.2.6: export RTE_TARGET=x86_64-native-linuxapp-gcc<o:p></o:p> 08/05/2018 03:22:12 dut.10.70.2.6:<o:p></o:p> 08/05/2018 03:22:12 dut.10.70.2.6: export RTE_SDK=`pwd`<o:p></o:p> 08/05/2018 03:22:12 dut.10.70.2.6:<o:p></o:p> 08/05/2018 03:22:12 dut.10.70.2.6: rm -rf x86_64-native-linuxapp-gcc<o:p></o:p> 08/05/2018 03:22:12 dut.10.70.2.6:<o:p></o:p> 08/05/2018 03:22:12 dut.10.70.2.6: rm -rf ./app/test/test_resource_c.res.o<o:p></o:p> 08/05/2018 03:22:12 dut.10.70.2.6:<o:p></o:p> 08/05/2018 03:22:12 dut.10.70.2.6: rm -rf ./app/test/test_resource_tar.res.o<o:p></o:p> 08/05/2018 03:22:12 dut.10.70.2.6:<o:p></o:p> 08/05/2018 03:22:12 dut.10.70.2.6: rm -rf ./app/test/test_pci_sysfs.res.o<o:p></o:p> 08/05/2018 03:22:12 dut.10.70.2.6:<o:p></o:p> 08/05/2018 03:22:12 dut.10.70.2.6: make -j 19 install T=x86_64-native-linuxapp-gcc<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: /bin/sh: line 1: cc: command not found<o:p></o:p> cat: /root/dpdk/x86_64-native-linuxapp-gcc/.config_tmp: No such file or directory<o:p></o:p> Configuration done using x86_64-native-linuxapp-gcc<o:p></o:p> /root/dpdk/mk/rte.vars.mk:56: *** RTE_ARCH is not defined. Stop.<o:p></o:p> /root/dpdk/mk/rte.sdkroot.mk:100: recipe for target 'all' failed<o:p></o:p> make[2]: *** [all] Error 2<o:p></o:p> /root/dpdk/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed<o:p></o:p> make[1]: *** [pre_install] Error 2<o:p></o:p> /root/dpdk/mk/rte.sdkroot.mk:79: recipe for target 'install' failed<o:p></o:p> make: *** [install] Error 2<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: make -j 19 -C test/<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: make: Entering directory '/root/dpdk/test'<o:p></o:p> /root/dpdk/mk/rte.vars.mk:56: *** RTE_ARCH is not defined. Stop.<o:p></o:p> make: Leaving directory '/root/dpdk/test'<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: cp -f ./test/test/test ./x86_64-native-linuxapp-gcc/app<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: cp: cannot stat ‘./test/test/test’: No such file or directory<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: cp -f ./test/test-acl/testacl ./x86_64-native-linuxapp-gcc/app<o:p></o:p> 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></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: cp -f ./test/test-pipeline/testpipeline ./x86_64-native-linuxapp-gcc/app<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: cp: cannot stat ‘./test/test-pipeline/testpipeline’: No such file or directory<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: cp -f ./test/cmdline_test/cmdline_test ./x86_64-native-linuxapp-gcc/app<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: cp: cannot stat ‘./test/cmdline_test/cmdline_test’: No such file or directory<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: ERROR - try without '-j'<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: make install T=x86_64-native-linuxapp-gcc<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: /bin/sh: line 1: cc: command not found<o:p></o:p> cat: /root/dpdk/x86_64-native-linuxapp-gcc/.config_tmp: No such file or directory<o:p></o:p> Configuration done using x86_64-native-linuxapp-gcc<o:p></o:p> /root/dpdk/mk/rte.vars.mk:56: *** RTE_ARCH is not defined. Stop.<o:p></o:p> /root/dpdk/mk/rte.sdkroot.mk:100: recipe for target 'all' failed<o:p></o:p> make[2]: *** [all] Error 2<o:p></o:p> /root/dpdk/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed<o:p></o:p> make[1]: *** [pre_install] Error 2<o:p></o:p> /root/dpdk/mk/rte.sdkroot.mk:79: recipe for target 'install' failed<o:p></o:p> make: *** [install] Error 2<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: make -j 19 -C test/<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: make: Entering directory '/root/dpdk/test'<o:p></o:p> /root/dpdk/mk/rte.vars.mk:56: *** RTE_ARCH is not defined. Stop.<o:p></o:p> make: Leaving directory '/root/dpdk/test'<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: cp -f ./test/test/test ./x86_64-native-linuxapp-gcc/app<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: cp: cannot stat ‘./test/test/test’: No such file or directory<o:p></o:p> 08/05/2018 03:22:13 dut.10.70.2.6: cp -f ./test/test-acl/testacl ./x86_64-native-linuxapp-gcc/app<o:p></o:p> 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></o:p> 08/05/2018 03:22:14 dut.10.70.2.6: cp -f ./test/test-pipeline/testpipeline ./x86_64-native-linuxapp-gcc/app<o:p></o:p> 08/05/2018 03:22:14 dut.10.70.2.6: cp: cannot stat ‘./test/test-pipeline/testpipeline’: No such file or directory<o:p></o:p> 08/05/2018 03:22:14 dut.10.70.2.6: cp -f ./test/cmdline_test/cmdline_test ./x86_64-native-linuxapp-gcc/app<o:p></o:p> 08/05/2018 03:22:14 dut.10.70.2.6: cp: cannot stat ‘./test/cmdline_test/cmdline_test’: No such file or directory<o:p></o:p> 08/05/2018 03:22:14 dts: TARGET ERROR: Compilation error...<o:p></o:p> </td> </tr> </tbody> </table> <o:p> </o:p> Could you kindly help me understand as to why I am facing this error – I understand that once we have configured 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.<o:p></o:p> <o:p> </o:p> Kindly do let me know if am missing anything here.<o:p></o:p> <o:p> </o:p> The configurations on my TESTER machine are as follows:<o:p></o:p> <o:p> </o:p> <table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="background:#FBE4D5;border-collapse:collapse"> <tbody> <tr> <td width="559" valign="top" style="width:512.6pt;border:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt"> [root@tester dts]# cat conf/ports.cfg<o:p></o:p> # DUT Port Configuration<o:p></o:p> # [DUT IP]<o:p></o:p> # ports=<o:p></o:p> # pci=Pci BDF,intf=Kernel interface;<o:p></o:p> # pci=Pci BDF,mac=Mac address,peer=Tester Pci BDF,numa=Port Numa<o:p></o:p> # pci=Pci BDF,peer=IXIA:card.port<o:p></o:p> # pci=Pci BDF,peer=Tester Pci BDF,tp_ip=$(IP),tp_path=$({PERL_PATH);<o:p></o:p> # pci=Pci BDF,peer=Tester Pci BDF,sec_port=yes,first_port=Pci BDF;<o:p></o:p> # [VM NAME] virtual machine name; This section is for virutal scenario<o:p></o:p> # ports =<o:p></o:p> # dev_idx=device index of ports info, peer=Tester Pci BDF<o:p></o:p> [10.70.2.6]<o:p></o:p> ports =<o:p></o:p> pci=05:00.0,intf=ens2f0;<o:p></o:p> pci=05:00.1,intf=ens2f1;<o:p></o:p> </td> </tr> </tbody> </table> <o:p> </o:p> <o:p> </o:p> <table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="background:#FBE4D5;border-collapse:collapse"> <tbody> <tr> <td width="559" valign="top" style="width:512.6pt;border:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt"> [root@tester dts]# cat executions/execution.cfg<o:p></o:p> [Execution1]<o:p></o:p> crbs=10.70.2.6<o:p></o:p> drivername=igb_uio<o:p></o:p> test_suites=hello_world<o:p></o:p> test_suites=<o:p></o:p> cmdline,<o:p></o:p> hello_world<o:p></o:p> targets=x86_64-native-linuxapp-gcc<o:p></o:p> parameters=nic_type=niantic:func=true<o:p></o:p> </td> </tr> </tbody> </table> <o:p> </o:p> <o:p> </o:p> <table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="background:#FBE4D5;border-collapse:collapse"> <tbody> <tr> <td width="559" valign="top" style="width:512.6pt;border:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt"> [root@tester dts]# cat conf/crbs.cfg<o:p></o:p> #DUT crbs Configuration<o:p></o:p> #[DUT IP]<o:p></o:p> # dut_ip: DUT ip address<o:p></o:p> # dut_user: Login DUT username<o:p></o:p> # dut_passwd: Login DUT password<o:p></o:p> # os: operation system type linux or freebsd<o:p></o:p> # tester_ip: Tester ip address<o:p></o:p> # tester_passwd: Tester password<o:p></o:p> # ixia_group: IXIA group name<o:p></o:p> # channels: Board channel number<o:p></o:p> # bypass_core0: Whether by pass core0<o:p></o:p> [10.70.2.6]<o:p></o:p> dut_ip=10.70.2.6<o:p></o:p> dut_user=root<o:p></o:p> dut_passwd=HP1nvent<o:p></o:p> os=fedora<o:p></o:p> tester_ip=10.70.2.5<o:p></o:p> tester_passwd=HP1nvent<o:p></o:p> channels=4<o:p></o:p> </td> </tr> </tbody> </table> <o:p> </o:p> <o:p> </o:p> Thanking in advance,<o:p></o:p> Chengappa<o:p></o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: Liu, Yong [<a href="mailto:yong.liu@intel.com">mailto:yong.liu@intel.com</a>] Sent: Friday, May 04, 2018 2:52 PM To: Liu, Yong <<a href="mailto:yong.liu@intel.com">yong.liu@intel.com</a>>; M R, Chengappa (Network Function Virtualization) <<a href="mailto:cm-r@hpe.com">cm-r@hpe.com</a>>; <a href="mailto:dts@dpdk.org">dts@dpdk.org</a> Subject: RE: DPDK Test Suite: execution of full test cases<o:p></o:p> </div> </div> <o:p> </o:p> Chengappa,<o:p></o:p> You can also utilize verbose and debug option for DTS issue debugging.<o:p></o:p> Command will like:<o:p></o:p> ./dts --debug –v<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> Marvin<o:p></o:p> <o:p> </o:p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: dts [<a href="mailto:dts-bounces@dpdk.org">mailto:dts-bounces@dpdk.org</a>] On Behalf Of Liu, Yong Sent: Friday, May 04, 2018 4:33 PM To: M R, Chengappa (Network Function Virtualization) <<a href="mailto:cm-r@hpe.com">cm-r@hpe.com</a>>; <a href="mailto:dts@dpdk.org">dts@dpdk.org</a> Subject: Re: [dts] DPDK Test Suite: execution of full test cases<o:p></o:p> </div> </div> <o:p> </o:p> Hi Chengappa,<o:p></o:p> Welcome to DTS community. <o:p></o:p> The detail running log of DTS will located at output/dts.log. You can check the error when building dpdk in the log file. <o:p></o:p> DTS master branch now supporting dpdk v18.02. If you are testing other versions of DPDK, you may need to switch DTS version.<o:p></o:p> <o:p> </o:p> DTS tutorial is at <a href="http://dpdk.org/doc/dts/gsg/tutorial.html"> http://dpdk.org/doc/dts/gsg/tutorial.html</a>. You can reference to it.<o:p></o:p> <o:p> </o:p> Thanks, Marvin<o:p></o:p> <o:p> </o:p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: dts [<a href="mailto:dts-bounces@dpdk.org">mailto:dts-bounces@dpdk.org</a>] On Behalf Of M R, Chengappa (Network Function Virtualization) Sent: Thursday, May 03, 2018 6:19 PM To: <a href="mailto:dts@dpdk.org">dts@dpdk.org</a> Subject: [dts] DPDK Test Suite: execution of full test cases<o:p></o:p> </div> </div> <o:p> </o:p> Hello Team, <o:p></o:p> Greetings!<o:p></o:p> <o:p> </o:p> We are aiming to install DTS and execute the test cases which are part of DTS framework.<o:p></o:p> <o:p> </o:p> However, we are frequently facing issues and currently failing to execute the test cases.<o:p></o:p> <o:p> </o:p> Currently we are blocked as we are encountering the issue which is describer here – <o:p></o:p> <a href="http://dpdk.org/ml/archives/dts/2018-May/003990.html">http://dpdk.org/ml/archives/dts/2018-May/003990.html</a><o:p></o:p> <o:p> </o:p> Am initiating this thread to check –<o:p></o:p> <o:p> </o:p> <![if !supportLists]>1. <![endif]>Is there any logging options enabled with DTS so that we could see the log traces<o:p></o:p> <o:p> </o:p> <![if !supportLists]>2. <![endif]>Also need to understand if anyone here in this community who has exercised end-to-end DPDK test suite with all the test cases – if so would like to understand what is the running configuration on TESTER and TARGET DUT<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Thanking in advance,<o:p></o:p> Chengappa<o:p></o:p> </div> </div> </div> </div> </body> </html>