test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: "M R, Chengappa (Network Function Virtualization)" <cm-r@hpe.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] DPDK Test Suite: execution of full test cases
Date: Tue, 8 May 2018 06:45:24 +0000	[thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E63037191@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <TU4PR8401MB0654818B5100AC829E03CF9D999A0@TU4PR8401MB0654.NAMPRD84.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 10162 bytes --]

Welcome Chengappa.

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.
You need installed required packets for building. Reference link: http://dpdk.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 prepare 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=linux

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 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@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@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@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@intel.com]
Sent: Friday, May 04, 2018 2:52 PM
To: Liu, Yong <yong.liu@intel.com<mailto:yong.liu@intel.com>>; M R, Chengappa (Network Function Virtualization) <cm-r@hpe.com<mailto:cm-r@hpe.com>>; dts@dpdk.org<mailto: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) <cm-r@hpe.com<mailto:cm-r@hpe.com>>; dts@dpdk.org<mailto: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 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<mailto: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 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

[-- Attachment #2: Type: text/html, Size: 39463 bytes --]

  reply	other threads:[~2018-05-08  6:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 10:19 M R, Chengappa (Network Function Virtualization)
2018-05-04  8:33 ` Liu, Yong
2018-05-04  9:22   ` Liu, Yong
2018-05-08  6:13     ` M R, Chengappa (Network Function Virtualization)
2018-05-08  6:45       ` Liu, Yong [this message]
2018-05-08 11:02         ` M R, Chengappa (Network Function Virtualization)
2018-05-09  1:52           ` Liu, Yong
2018-05-09  3:11             ` M R, Chengappa (Network Function Virtualization)

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=86228AFD5BCD8E4EBFD2B90117B5E81E63037191@SHSMSX103.ccr.corp.intel.com \
    --to=yong.liu@intel.com \
    --cc=cm-r@hpe.com \
    --cc=dts@dpdk.org \
    /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).