From: "Yao, Lei A" <lei.a.yao@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Mo, YufengX" <yufengx.mo@intel.com>
Subject: Re: [dts] [PATCH V1 2/2] tests/vm_power_manager: fix typo in output message
Date: Wed, 10 Jul 2019 08:31:32 +0000 [thread overview]
Message-ID: <2DBBFF226F7CF64BAFCA79B681719D954972F9DA@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1562728162-214888-3-git-send-email-yufengx.mo@intel.com>
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yufengmx
> Sent: Wednesday, July 10, 2019 11:09 AM
> To: dts@dpdk.org
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts] [PATCH V1 2/2] tests/vm_power_manager: fix typo in output
> message
>
>
> fix typo issue in output message.
>
> Signed-off-by: yufengmx <yufengx.mo@intel.com>
Acked-by: Lei Yao <lei.a.yao@intel.com>
> ---
> tests/TestSuite_vm_power_manager.py | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/tests/TestSuite_vm_power_manager.py
> b/tests/TestSuite_vm_power_manager.py
> index 7620c19..1b9a965 100644
> --- a/tests/TestSuite_vm_power_manager.py
> +++ b/tests/TestSuite_vm_power_manager.py
> @@ -151,7 +151,7 @@ class TestVmPowerManager(TestCase,
> IxiaPacketGenerator):
> self.vm_dut.send_expect(
> "set_cpu_freq %d down" % vcpu, "vmpower\(guest\)>")
> cur_freq = self.get_cpu_frequency(self.vcpu_map[vcpu])
> - print utils.GREEN("After freqency down, freq is %d\n" % cur_freq)
> + print utils.GREEN("After frequency down, freq is %d\n" % cur_freq)
> self.verify(
> ori_freq > cur_freq, "Cpu freqenecy can not scale down")
> ori_freq = cur_freq
> @@ -178,7 +178,7 @@ class TestVmPowerManager(TestCase,
> IxiaPacketGenerator):
> self.vm_dut.send_expect(
> "set_cpu_freq %d up" % vcpu, "vmpower\(guest\)>")
> cur_freq = self.get_cpu_frequency(self.vcpu_map[vcpu])
> - print utils.GREEN("After freqency up, freq is %d\n" % cur_freq)
> + print utils.GREEN("After frequency up, freq is %d\n" % cur_freq)
> self.verify(
> cur_freq > ori_freq, "Cpu freqenecy can not scale up")
> ori_freq = cur_freq
> @@ -205,7 +205,7 @@ class TestVmPowerManager(TestCase,
> IxiaPacketGenerator):
> max_freq = int(out)
>
> self.verify(freq == max_freq, "Cpu max frequency not correct")
> - print utils.GREEN("After freqency max, freq is %d\n" % max_freq)
> + print utils.GREEN("After frequency max, freq is %d\n" % max_freq)
> self.vm_dut.send_expect("quit", "# ")
>
> def test_vm_power_managment_freqmin(self):
> @@ -228,7 +228,7 @@ class TestVmPowerManager(TestCase,
> IxiaPacketGenerator):
> min_freq = int(out)
>
> self.verify(freq == min_freq, "Cpu min frequency not correct")
> - print utils.GREEN("After freqency min, freq is %d\n" % min_freq)
> + print utils.GREEN("After frequency min, freq is %d\n" % min_freq)
> self.vm_dut.send_expect("quit", "# ")
>
> def test_vm_power_multivms(self):
> @@ -269,7 +269,7 @@ class TestVmPowerManager(TestCase,
> IxiaPacketGenerator):
> cpu_idx = 0
> for cpu in cpus:
> cpu_map = '[%d]: Physical CPU %s' % (cpu_idx, cpu)
> - self.verify(cpu_map in vm_info, "Faile to map host cpu %s" % cpu)
> + self.verify(cpu_map in vm_info, "Failed to map host cpu %s" % cpu)
> cpu_idx += 1
>
> out =
> vm2_dut.build_dpdk_apps("examples/vm_power_manager/guest_cli")
> --
> 1.9.3
next prev parent reply other threads:[~2019-07-10 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 3:09 [dts] [PATCH V1 0/2] dts/tests: " yufengmx
2019-07-10 3:09 ` [dts] [PATCH V1 1/2] tests/kni: " yufengmx
2019-07-10 8:28 ` Yao, Lei A
2019-07-10 3:09 ` [dts] [PATCH V1 2/2] tests/vm_power_manager: " yufengmx
2019-07-10 8:31 ` Yao, Lei A [this message]
2019-08-06 10:08 ` 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=2DBBFF226F7CF64BAFCA79B681719D954972F9DA@shsmsx102.ccr.corp.intel.com \
--to=lei.a.yao@intel.com \
--cc=dts@dpdk.org \
--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).