From: "Mo, YufengX" <yufengx.mo@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Cc: "Peng, Yuan" <yuan.peng@intel.com>,
"Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dts] [PATCH V1 1/1] tests/flow_classify_softnic: fix target source code
Date: Mon, 16 Sep 2019 01:50:59 +0000 [thread overview]
Message-ID: <B8B15C44A3F2C044966E545C7B7371153E849216@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20190912075440.19444-2-yufengx.mo@intel.com>
tested by Mo, YufengX <yufengx.mo@intel.com>
> -----Original Message-----
> From: Mo, YufengX
> Sent: Thursday, September 12, 2019 3:55 PM
> To: dts@dpdk.org; Peng, Yuan <yuan.peng@intel.com>; Li, WenjieX A <wenjiex.a.li@intel.com>
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts][PATCH V1 1/1] tests/flow_classify_softnic: fix target source code
>
> directory issue
>
> change hard code of target source code directory.
>
> Signed-off-by: yufengmx <yufengx.mo@intel.com>
> ---
> tests/TestSuite_flow_classify_softnic.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_flow_classify_softnic.py b/tests/TestSuite_flow_classify_softnic.py
> index a649a44..33f701e 100644
> --- a/tests/TestSuite_flow_classify_softnic.py
> +++ b/tests/TestSuite_flow_classify_softnic.py
> @@ -72,7 +72,7 @@ class TestFlowClassifySoftnic(TestCase):
> file = 'flow_classify_softnic.tar.gz'
> src_file = r'./dep/%s' % file
> dst1 = '/tmp'
> - dst2 = '/root/dpdk/drivers/net/softnic'
> + dst2 = os.path.join(self.dut.base_dir, 'drivers/net/softnic')
> self.dut.session.copy_file_to(src_file, dst1)
> self.dut.send_expect("tar xf %s/%s -C %s" % (dst1, file, dst2), "#", 30)
>
> --
> 2.21.0
next prev parent reply other threads:[~2019-09-16 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 7:54 [dts] [PATCH V1 0/1] tests/flow_classify_softnic: fix target source code directory issue yufengmx
2019-09-12 7:54 ` [dts] [PATCH V1 1/1] tests/flow_classify_softnic: fix target source code yufengmx
2019-09-16 1:50 ` Mo, YufengX [this message]
2019-09-20 6:21 ` Tu, Lijuan
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=B8B15C44A3F2C044966E545C7B7371153E849216@shsmsx102.ccr.corp.intel.com \
--to=yufengx.mo@intel.com \
--cc=dts@dpdk.org \
--cc=wenjiex.a.li@intel.com \
--cc=yuan.peng@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).