From: "Qiu, Michael" <michael.qiu@intel.com>
To: "Gu, YongjieX" <yongjiex.gu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] add testsuite coremask
Date: Wed, 14 Oct 2015 08:24:30 +0000 [thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E6028621B49026@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1444788543-70429-2-git-send-email-yongjiex.gu@intel.com>
First I would like to know what's the purpose this case, if you could
describe it in the commit log, it would help others to understand.
On 2015/10/14 10:13, yongjie wrote:
> From: GuYongjie <yongjiex.gu@intel.com>
>
> Signed-off-by: GuYongjie <yongjiex.gu@intel.com>
> ---
> tests/TestSuite_coremask.py | 189 ++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 189 insertions(+)
> create mode 100644 tests/TestSuite_coremask.py
>
> diff --git a/tests/TestSuite_coremask.py b/tests/TestSuite_coremask.py
> new file mode 100644
> index 0000000..3520a9c
> --- /dev/null
> +++ b/tests/TestSuite_coremask.py
> @@ -0,0 +1,189 @@
> +# <COPYRIGHT_TAG>
> +
> +"""
> +DPDK Test suite.
> +
> +Test coremask parsing in DPDK.
> +
[.../...]
> + def test_wrong_coremask(self):
> + """
> + Check coremask parsing for wrong coremasks.
> + """
> +
> + wrong_coremasks = ["GARBAGE", "0xJF", "0xFJF", "0xFFJ",
> + "0xJ11", "0x1J1", "0x11J",
> + "JF", "FJF", "FFJ",
> + "J11", "1J1", "11J",
> + "jf", "fjf", "ffj",
> + "FF0x", "ff0x", "", "0x", "0"]
> +
Here I think, the value contains "J" or other none [a~f] should be only
one entry, other wrong value could be the mask which greater the cpu
number,
Thanks,
Michael
> + for coremask in wrong_coremasks:
> +
> + command = command_line % (self.target, coremask, self.mem_channel)
> + try:
> + out = self.dut.send_expect(command, "# ", 5)
> + self.verify("EAL: invalid coremask" in out,
> + "Wrong core mask (%s) accepted" % coremask)
> + except:
> + self.dut.send_expect("quit", "# ", 5)
> + raise VerifyFailure("Wrong core mask (%s) accepted" % coremask)
> +
> + def tear_down(self):
> + """
> + Run after each test case.
> + """
> + self.dut.kill_all()
> +
> + def tear_down_all(self):
> + """
> + Run after each test suite.
> + """
> + pass
next prev parent reply other threads:[~2015-10-14 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 2:09 [dts] [PATCH] add coremask test plan yongjie
2015-10-14 2:09 ` [dts] [PATCH] add testsuite coremask yongjie
2015-10-14 8:24 ` Qiu, Michael [this message]
2015-10-22 7:26 [dts] [PATCH] add coremask test plan yongjie
2015-10-22 7:26 ` [dts] [PATCH] add testsuite coremask yongjie
2015-10-22 7:31 yongjie
2015-10-22 8:22 yongjie
2015-10-23 1:03 ` 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=533710CFB86FA344BFBF2D6802E6028621B49026@SHSMSX101.ccr.corp.intel.com \
--to=michael.qiu@intel.com \
--cc=dts@dpdk.org \
--cc=yongjiex.gu@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).