From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>, "Yao, Lei A" <lei.a.yao@intel.com>
Cc: "Mo, YufengX" <yufengx.mo@intel.com>
Subject: Re: [dts] [PATCH V2 1/1] tests/vm_pw_mgmt_policy: resolve centos compatibility
Date: Mon, 20 Jul 2020 06:59:06 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC821D6@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200706044045.24841-2-yufengx.mo@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of yufengmx
> Sent: 2020年7月6日 12:41
> To: dts@dpdk.org; Yao, Lei A <lei.a.yao@intel.com>
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts] [PATCH V2 1/1] tests/vm_pw_mgmt_policy: resolve centos
> compatibility
>
>
> resolve centos compatibility.
>
> Signed-off-by: yufengmx <yufengx.mo@intel.com>
> ---
> tests/TestSuite_vm_pw_mgmt_policy.py | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/tests/TestSuite_vm_pw_mgmt_policy.py
> b/tests/TestSuite_vm_pw_mgmt_policy.py
> index 00c7304..37f49e4 100644
> --- a/tests/TestSuite_vm_pw_mgmt_policy.py
> +++ b/tests/TestSuite_vm_pw_mgmt_policy.py
> @@ -473,7 +473,8 @@ class TestVmPwMgmtPolicy(TestCase):
> date_tool = "date"
> cmd = ';'.join([
> "{0}",
> - "{0} -s \'{1}\'",
> + "{0} -s 0",
> + "{0} -s '{1}'",
> "hwclock -w"]).format(date_tool, timestamp)
> self.d_a_con([cmd, '# ', 20])
> cmd = "{0} '+%H:00'".format(date_tool) @@ -498,7 +499,7 @@ class
> TestVmPwMgmtPolicy(TestCase):
> real_time = timestamp.strftime(FMT)
> cmd = ';'.join([
> "{0}",
> - "{0} -s \'{1}\'",
> + "{0} -s '{1}'",
> "hwclock -w",
> "{0}", ]).format(date_tool, real_time)
> self.d_a_con([cmd, '# ', 20])
> @@ -537,7 +538,7 @@ class TestVmPwMgmtPolicy(TestCase):
> if key_value == 'scaling_available_frequencies':
> cpu_info[cpu_id][key_value] = freqs[index]
> cpu_info[cpu_id][key_value] = \
> - [int(item) for item in sorted(freqs[index].split())] \
> + sorted([int(item) for item in
> + sorted(freqs[index].split())]) \
> if key_value == 'scaling_available_frequencies' else \
> freqs[index]
>
> --
> 2.21.0
prev parent reply other threads:[~2020-07-20 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 4:40 [dts] [PATCH V2 0/1] vm_pw_mgmt_policy: " yufengmx
2020-07-06 4:40 ` [dts] [PATCH V2 1/1] tests/vm_pw_mgmt_policy: " yufengmx
2020-07-20 6:59 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0BC821D6@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=lei.a.yao@intel.com \
--cc=yufengx.mo@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).