NVDIMM Device and Persistent Memory development
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Ira Weiny <ira.weiny@intel.com>,
	Alison Schofield <alison.schofield@intel.com>
Cc: Vishal Verma <vishal.l.verma@intel.com>,
	Jonathan Cameron <jonathan.cameron@Huawei.com>,
	Fan Ni <fan.ni@samsung.com>,
	Navneet Singh <navneet.singh@intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev
Subject: Re: [ndctl PATCH v2 1/6] ndctl/cxl-events: Don't fail test until event counts are reported
Date: Tue, 5 Nov 2024 08:44:46 -0700	[thread overview]
Message-ID: <37e180b0-df8b-4fc6-bd40-3779eba47030@intel.com> (raw)
In-Reply-To: <20241104-dcd-region2-v2-1-be057b479eeb@intel.com>



On 11/4/24 7:10 PM, Ira Weiny wrote:
> In testing DCD event modifications a failed cxl-event test lacked
> details on the event counts.  This was because the greps were failing
> the test rather than the check against the counts.
> 
> Suppress the grep failure and rely on event count checks for pass/fail
> of the test.
> 
> Signed-off-by: Ira Weiny <ira.weiny@intel.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>

> ---
>  test/cxl-events.sh | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/test/cxl-events.sh b/test/cxl-events.sh
> index ff4f3fdff1d8f6fd80f093126a27bf14b52d167f..c216d6aa9148c938a649cb22656127b3df440039 100644
> --- a/test/cxl-events.sh
> +++ b/test/cxl-events.sh
> @@ -71,10 +71,10 @@ echo 0 > /sys/kernel/tracing/tracing_on
>  echo "TEST: Events seen"
>  trace_out=$(cat /sys/kernel/tracing/trace)
>  
> -num_overflow=$(grep -c "cxl_overflow" <<< "${trace_out}")
> -num_fatal=$(grep -c "log=Fatal" <<< "${trace_out}")
> -num_failure=$(grep -c "log=Failure" <<< "${trace_out}")
> -num_info=$(grep -c "log=Informational" <<< "${trace_out}")
> +num_overflow=$(grep -c "cxl_overflow" <<< "${trace_out}" || true)
> +num_fatal=$(grep -c "log=Fatal" <<< "${trace_out}" || true)
> +num_failure=$(grep -c "log=Failure" <<< "${trace_out}" || true)
> +num_info=$(grep -c "log=Informational" <<< "${trace_out}" || true)
>  echo "     LOG     (Expected) : (Found)"
>  echo "     overflow      ($num_overflow_expected) : $num_overflow"
>  echo "     Fatal         ($num_fatal_expected) : $num_fatal"
> 


  reply	other threads:[~2024-11-05 15:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05  2:10 [ndctl PATCH v2 0/6] ndctl: DCD additions Ira Weiny
2024-11-05  2:10 ` [ndctl PATCH v2 1/6] ndctl/cxl-events: Don't fail test until event counts are reported Ira Weiny
2024-11-05 15:44   ` Dave Jiang [this message]
2025-02-09  1:25   ` Alison Schofield
2024-11-05  2:10 ` [ndctl PATCH v2 2/6] ndctl/cxl/region: Report max size for region creation Ira Weiny
2024-11-05 15:45   ` Dave Jiang
2024-11-05 21:46   ` Fan Ni
2025-02-09  1:26   ` Alison Schofield
2024-11-05  2:10 ` [ndctl PATCH v2 3/6] ndctl: Separate region mode from decoder mode Ira Weiny
2024-11-05 15:56   ` Dave Jiang
2024-11-05 21:49   ` Fan Ni
2024-11-05  2:10 ` [ndctl PATCH v2 4/6] cxl/region: Add creation of Dynamic capacity regions ira.weiny
2024-11-05 16:38   ` Dave Jiang
2024-11-05 20:38     ` Ira Weiny
2024-11-06  3:16   ` Alison Schofield
2024-11-07 18:00   ` Alison Schofield
2024-11-07 21:28     ` Ira Weiny
2024-11-07 18:27   ` Alison Schofield
2024-11-07 18:52   ` Alison Schofield
2024-11-08 20:17     ` Ira Weiny
2024-11-05  2:10 ` [ndctl PATCH v2 5/6] ndctl/cxl: Add extent output to region query Ira Weiny
2024-11-05 17:04   ` Dave Jiang
2024-11-05 20:53     ` Ira Weiny
2024-11-07 18:13   ` Alison Schofield
2024-11-08 20:16     ` Ira Weiny
2024-11-05  2:10 ` [ndctl PATCH v2 6/6] ndctl/cxl/test: Add Dynamic Capacity tests Ira Weiny
2024-11-05 17:11   ` Dave Jiang
2024-11-05 19:53     ` 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=37e180b0-df8b-4fc6-bd40-3779eba47030@intel.com \
    --to=dave.jiang@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=fan.ni@samsung.com \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@Huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=navneet.singh@intel.com \
    --cc=nvdimm@lists.linux.dev \
    --cc=vishal.l.verma@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