From: "Liu, Yong" <yong.liu@intel.com>
To: "xueqin.lin" <xlin15@ecsmtp.sh.intel.com>, dts@dpdk.org
Cc: Xueqin Lin <xueqin.lin@intel.com>
Subject: Re: [dts] [PATCH] tests: add ftag test suite and plan
Date: Thu, 11 Aug 2016 09:54:29 +0800 [thread overview]
Message-ID: <57ABDAD5.4080204@intel.com> (raw)
In-Reply-To: <1470815735-10949-1-git-send-email-xlin15@shecgisg005.sh.intel.com>
Xueqin, one comment about dpdk build.
On 08/10/2016 03:55 PM, xueqin.lin wrote:
> + def set_up_all(self):
> + """
> + Run at the start of each test suite.
> + """
> + self.verify(self.nic in ['redrockcanyou','atwood','boulderrapid'], 'ftag test can not support %s nic'%self.nic)
> + self.ports = self.dut.get_ports(self.nic)
> + self.verify(len(self.ports) >= 2, "Insufficient number of ports.")
> + patch_file = r'dep/fm10k-add-a-unit-test-for-FTAG-based-forwarding.patch'
> + patch_dst = "/tmp/"
> + self.dut.session.copy_file_to(patch_file, patch_dst)
> + self.patch_hotfix_dpdk(patch_dst + "fm10k-add-a-unit-test-for-FTAG-based-forwarding.patch", True)
> + self.dut.send_expect("sed -i -e '/CONFIG_RTE_VIRTIO_USER=y/a\CONFIG_RTE_LIBRTE_FM10K_FTAG_FWD=y' config/common_linuxapp", "# ")
> + self.dut.send_expect("sed -i -e '/SRCS-y += test_pmd_perf.c/a\SRCS-y += test_fm10k_ftag.c' app/test/Makefile", "# ")
> + out = self.dut.send_expect("make install T=%s -j" %self.dut.target, "# ", 300)
> + self.verify('Build complete' in out, "Compilation failed")
You can use function self.dut.build_install_dpdk(self.target) to build dpdk.
It's better to rebuild dpdk in tear_down_all function.
next parent reply other threads:[~2016-08-11 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1470815735-10949-1-git-send-email-xlin15@shecgisg005.sh.intel.com>
2016-08-11 1:54 ` Liu, Yong [this message]
2016-08-11 1:56 ` Lin, Xueqin
[not found] <1470723536-16674-1-git-send-email-xlin15@shecgisg005.sh.intel.com>
2016-08-10 2:08 ` Liu, Yong
2016-08-10 6:31 ` Lin, Xueqin
2016-08-10 7:37 ` Liu, Yong
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=57ABDAD5.4080204@intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=xlin15@ecsmtp.sh.intel.com \
--cc=xueqin.lin@intel.com \
/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).