public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: "John Warthog9 Hawley" <warthog9@kernel.org>
Subject: [for-linus][PATCH 0/2] ktest: Fixes for v7.1
Date: Mon, 20 Apr 2026 15:32:03 -0400	[thread overview]
Message-ID: <20260420193203.993782513@kernel.org> (raw)

ktest updates for v7.1:

- Fix date timestamp of failure directory

  When a ktest fails, if STORE_FAILURES is set, then if a test fails, it
  copies various files to a created directory in the STORE_FAILURES
  location (like the .config used, and some other files). To create the
  timestamp portion of the directory name, the Perl function localtime() is
  used. The month field starts from 0 and the code does not account for
  this. That is, the date of April 20, 2026 will be displayed as 20260320
  instead of 20260420. Add one to the month to have the date be more
  accurate.

- Save the entire log file in the failure directory

  The logfile that keeps track of all tests contains boot messages, error
  messages, dmesg, etc. This information is very useful in figuring out why
  a test failed. Save the logfile in the failure directory as well.

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git
for-next

Head SHA1: 932cdaf3e273a2727e77af97f79f12577174c5a0


Steven Rostedt (2):
      ktest: Fix the month in the name of the failure directory
      ktest: Add logfile to failure directory

----
 tools/testing/ktest/ktest.pl | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

             reply	other threads:[~2026-04-20 19:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20 19:32 Steven Rostedt [this message]
2026-04-20 19:32 ` [for-linus][PATCH 1/2] ktest: Fix the month in the name of the failure directory Steven Rostedt
2026-04-20 19:32 ` [for-linus][PATCH 2/2] ktest: Add logfile to " Steven Rostedt

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=20260420193203.993782513@kernel.org \
    --to=rostedt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=warthog9@kernel.org \
    /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