From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Weiny, Ira" <ira.weiny@intel.com>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
"Jiang, Dave" <dave.jiang@intel.com>,
"Schofield, Alison" <alison.schofield@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>
Subject: Re: [PATCH ndctl v2] ndctl/cxl/test: Add CXL event test
Date: Tue, 1 Aug 2023 00:31:47 +0000 [thread overview]
Message-ID: <f65ef4e6cf9c93513ee6395c835553142db602eb.camel@intel.com> (raw)
In-Reply-To: <20230726-cxl-event-v2-1-550f5625d22f@intel.com>
On Mon, 2023-07-31 at 16:53 -0700, Ira Weiny wrote:
> Previously CXL event testing was run by hand. This reduces testing
Reduces or increases / improves? Or did you mean running by hand
reduced coverage.
Maybe this can read "Improve testing coverage and address a lack of
automated regression testing by adding a unit test for this"
(no need to respin, I can fixup when applying, just making sure I'm not
misinterpreting what you meant to say).
> coverage including a lack of regression testing.
>
> Add a CXL event test as part of the meson test infrastructure. Passing
> is predicated on receiving the appropriate number of errors in each log.
> Individual event values are not checked.
>
> Signed-off-by: Ira Weiny <ira.weiny@intel.com>
> ---
> Changes in v2:
> [djiang] run shellcheck and fix as needed
> [vishal] quote variables
> [vishal] skip test if event_trigger is not available
> [vishal] remove dead code
> [vishal] explicitly use the first memdev returned from cxl-cli
> [vishal] store trace output in a variable
> [vishal] simplify grep statement looking for results
> [vishal] use variables for expected values
> - Link to v1: https://lore.kernel.org/r/20230726-cxl-event-v1-1-1cf8cb02b211@intel.com
> ---
> test/cxl-events.sh | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> test/meson.build | 2 ++
> 2 files changed, 78 insertions(+)
>
Thanks for the rev, everything else looks good.
next prev parent reply other threads:[~2023-08-01 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 23:53 [PATCH ndctl v2] ndctl/cxl/test: Add CXL event test Ira Weiny
2023-08-01 0:31 ` Verma, Vishal L [this message]
2023-08-01 19:13 ` Ira Weiny
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=f65ef4e6cf9c93513ee6395c835553142db602eb.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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