test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Li, WenjieX A" <wenjiex.a.li@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Yao, Lei A" <lei.a.yao@intel.com>,
	"Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dts] [PATCH V2] tests/unit_tests_power: align changes with dpdk
Date: Wed, 10 Jul 2019 02:11:42 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BADE6FE@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1562597061-40418-1-git-send-email-wenjiex.a.li@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Wenjie Li
> Sent: Monday, July 8, 2019 10:44 PM
> To: dts@dpdk.org
> Cc: Yao, Lei A <lei.a.yao@intel.com>; Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts] [PATCH V2] tests/unit_tests_power: align changes with dpdk
> 
> In dpdk c7ec1f26fd6e6e64412, test_power_acpi_cpufreq and
> test_power_acpi_caps were changed to test_power_cpufreq and
> test_power_caps, align this change in dts.
> 
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> ---
>  tests/TestSuite_unit_tests_power.py | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/TestSuite_unit_tests_power.py
> b/tests/TestSuite_unit_tests_power.py
> index 1191168..4d90b88 100644
> --- a/tests/TestSuite_unit_tests_power.py
> +++ b/tests/TestSuite_unit_tests_power.py
> @@ -77,25 +77,25 @@ class TestUnitTestsPower(TestCase):
>          self.dut.send_expect("quit", "# ")
>          self.verify("Test OK" in out, "Test failed")
> 
> -    def test_power_acpi_cpufreq(self):
> +    def test_power_cpufreq(self):
>          """
>          Run power acpi cpu frequency autotest.
>          """
>          # This acpi driver test case need correct BIOS and Grub settings.
>          # otherwise, the power lib initialization will be failed
>          self.dut.send_expect("./%s/app/test -n 1 -c %s" % (self.target,
> self.coremask), "R.*T.*E.*>.*>", 60)
> -        out = self.dut.send_expect("power_acpi_cpufreq_autotest", "RTE>>",
> 60)
> +        out = self.dut.send_expect("power_cpufreq_autotest", "RTE>>",
> + 60)
>          self.dut.send_expect("quit", "# ")
>          self.verify("Test OK" in out, "Test failed")
> 
> -    def test_power_acpi_caps(self):
> +    def test_power_caps(self):
>          """
>          Run power acpi cpu caps autotest.
>          """
>          # This acpi driver test case need correct BIOS and Grub settings.
>          # otherwise, the power lib initialization will be failed
>          self.dut.send_expect("./%s/app/test -n 1 -c %s" % (self.target,
> self.coremask), "R.*T.*E.*>.*>", 60)
> -        out = self.dut.send_expect("power_acpi_caps_autotest", "RTE>>", 60)
> +        out = self.dut.send_expect("power_caps_autotest", "RTE>>", 60)
>          self.dut.send_expect("quit", "# ")
>          self.verify("Test OK" in out, "Test failed")
> 
> --
> 2.17.1


      reply	other threads:[~2019-07-10  2:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08 14:44 Wenjie Li
2019-07-10  2:11 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BADE6FE@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=lei.a.yao@intel.com \
    --cc=wenjiex.a.li@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).