[dts] DPDK Test Suite: execution of full test cases

M R, Chengappa (Network Function Virtualization) cm-r at hpe.com
Tue May 8 08:13:14 CEST 2018
Previous message: [dts] DPDK Test Suite: execution of full test cases
Next message: [dts] DPDK Test Suite: execution of full test cases
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Greetings Marvin,

Thank you for welcoming me to DTS community - looking forward for some great 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 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=x86_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=`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-linuxapp-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=x86_64-native-linuxapp-gcc
08/05/2018 03:22:13                  dut.10.70.2.6: /bin/sh: line 1: cc: command not found
cat: /root/dpdk/x86_64-native-linuxapp-gcc/.config_tmp: No such file or directory
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 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 ./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/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
08/05/2018 03:22:13                  dut.10.70.2.6: cp -f ./test/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 directory
08/05/2018 03:22:13                  dut.10.70.2.6: cp -f ./test/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 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=x86_64-native-linuxapp-gcc
08/05/2018 03:22:13                  dut.10.70.2.6: /bin/sh: line 1: cc: command not found
cat: /root/dpdk/x86_64-native-linuxapp-gcc/.config_tmp: No such file or directory
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 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 ./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/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
08/05/2018 03:22:14                  dut.10.70.2.6: cp -f ./test/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 directory
08/05/2018 03:22:14                  dut.10.70.2.6: cp -f ./test/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 directory
08/05/2018 03:22:14                            dts:  TARGET ERROR: Compilation error...


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.

Kindly do let me know if am missing anything here.

The configurations on my TESTER machine are as follows:

[root at tester dts]# cat conf/ports.cfg
# DUT Port Configuration
# [DUT IP]
# ports=
#     pci=Pci BDF,intf=Kernel interface;
#     pci=Pci BDF,mac=Mac address,peer=Tester Pci BDF,numa=Port Numa
#     pci=Pci BDF,peer=IXIA:card.port
#     pci=Pci BDF,peer=Tester Pci BDF,tp_ip=$(IP),tp_path=$({PERL_PATH);
#     pci=Pci BDF,peer=Tester Pci BDF,sec_port=yes,first_port=Pci BDF;
# [VM NAME] virtual machine name; This section is for virutal scenario
# ports =
#     dev_idx=device index of ports info, peer=Tester Pci BDF
[10.70.2.6]
ports =
    pci=05:00.0,intf=ens2f0;
    pci=05:00.1,intf=ens2f1;



[root at tester dts]# cat executions/execution.cfg
[Execution1]
crbs=10.70.2.6
drivername=igb_uio
test_suites=hello_world
test_suites=
    cmdline,
    hello_world
targets=x86_64-native-linuxapp-gcc
parameters=nic_type=niantic:func=true



[root at 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=10.70.2.6
dut_user=root
dut_passwd=HP1nvent
os=fedora
tester_ip=10.70.2.5
tester_passwd=HP1nvent
channels=4



Thanking in advance,
Chengappa

From: Liu, Yong [mailto:yong.liu at intel.com]
Sent: Friday, May 04, 2018 2:52 PM
To: Liu, Yong <yong.liu at intel.com>; M R, Chengappa (Network Function Virtualization) <cm-r at hpe.com>; dts at 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 at dpdk.org] On Behalf Of Liu, Yong
Sent: Friday, May 04, 2018 4:33 PM
To: M R, Chengappa (Network Function Virtualization) <cm-r at hpe.com<mailto:cm-r at hpe.com>>; dts at dpdk.org<mailto:dts at 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 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 at dpdk.org] On Behalf Of M R, Chengappa (Network Function Virtualization)
Sent: Thursday, May 03, 2018 6:19 PM
To: dts at dpdk.org<mailto:dts at 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 DTS framework.

However, we are frequently facing 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 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 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



Thanking in advance,
Chengappa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://dpdk.org/ml/archives/dts/attachments/20180508/720a1b22/attachment.html>
Previous message: [dts] DPDK Test Suite: execution of full test cases
Next message: [dts] DPDK Test Suite: execution of full test cases
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the dts mailing list