From: marc.herbert@linux.intel.com
To: linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev,
alison.schofield@intel.com, dan.j.williams@intel.com,
dave.jiang@intel.com
Subject: test/common: stop relying on bash $SECONDS in check_dmesg()
Date: Thu, 24 Jul 2025 22:00:43 +0000 [thread overview]
Message-ID: <20250724221323.365191-1-marc.herbert@linux.intel.com> (raw)
As requested, this is the broken-down, first part of
https://lore.kernel.org/linux-cxl/20250611235256.3866724-1-marc.herbert@linux.intel.com/
test: fail on unexpected kernel error & warning, not just "Call Trace"
I will resubmit the rest after the review of this first part is
completed. The different parts are logically separate (different
"features") but they are interleaved in the same function and I don't
really have the time to fix one git conflict per review comment.
While it is a requirement to catch warnings and errors later, the
better accuracy provided by this first part is useful alone. If you
are interested in what's next, just look at the bigger patch above.
You don't have to!
next reply other threads:[~2025-07-24 22:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 22:00 marc.herbert [this message]
2025-07-24 22:00 ` [ndctl PATCH 1/3] test/common: add missing quotes marc.herbert
2025-07-29 15:14 ` Dave Jiang
2025-08-06 21:43 ` Alison Schofield
2025-07-24 22:00 ` [ndctl PATCH 2/3] test/common: move err() function at the top marc.herbert
2025-07-29 15:14 ` Dave Jiang
2025-08-06 21:44 ` Alison Schofield
2025-07-24 22:00 ` [ndctl PATCH 3/3] test/common: stop relying on bash $SECONDS in check_dmesg() marc.herbert
2025-07-29 15:19 ` Dave Jiang
2025-08-22 0:10 ` Alison Schofield
2025-08-22 0:21 ` Alison Schofield
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=20250724221323.365191-1-marc.herbert@linux.intel.com \
--to=marc.herbert@linux.intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@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;
as well as URLs for NNTP newsgroup(s).