From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: kdevops@lists.linux.dev, Daniel Gomez <da.gomez@kruces.com>
Subject: Re: [PATCH 0/5] crash: provide a crash watchdog
Date: Mon, 21 Apr 2025 19:38:07 -0700 [thread overview]
Message-ID: <aAcBD_W2ASJyZeGQ@bombadil.infradead.org> (raw)
In-Reply-To: <aAbRvTmvZZ4lPb3X@bombadil.infradead.org>
On Mon, Apr 21, 2025 at 04:16:15PM -0700, Luis Chamberlain wrote:
> make ci-test
OK so here is an example change to get the mm tests leveraing now the
crash stuff watchdog:
https://github.com/linux-kdevops/kdevops-ci/commit/df620a59f6b5d88210f1f47efb616c68067c3767
I just pushed out a new test based on linux-next, as I reported recently
xarray currently crashes on its own selftests. *If* as of today's
linux-next that is still true, then the above *should* in theory finally
capture crashes (or fs corruption).
We'll know tomorrow if it worked.
Luis
prev parent reply other threads:[~2025-04-22 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-20 5:48 [PATCH 0/5] crash: provide a crash watchdog Luis Chamberlain
2025-04-20 5:48 ` [PATCH 1/5] systemd-remote: use ip address for systemd-remote journal Luis Chamberlain
2025-04-20 5:48 ` [PATCH 2/5] crash: add kernel crash watchdog library Luis Chamberlain
2025-04-20 5:48 ` [PATCH 3/5] fstests_watchdog.py: use the new " Luis Chamberlain
2025-04-20 5:48 ` [PATCH 4/5] crash_watchdog.py: add generic crash watchdog Luis Chamberlain
2025-04-20 5:48 ` [PATCH 5/5] crash_report.py: add a crash report Luis Chamberlain
2025-04-20 15:19 ` [PATCH 0/5] crash: provide a crash watchdog Chuck Lever
2025-04-21 23:16 ` Luis Chamberlain
2025-04-22 2:38 ` Luis Chamberlain [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=aAcBD_W2ASJyZeGQ@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=cel@kernel.org \
--cc=da.gomez@kruces.com \
--cc=kdevops@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