From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
John 'Warthog9' Hawley <warthog9@kernel.org>
Subject: [GIT PULL] ktest: Updates for 7.1
Date: Wed, 22 Apr 2026 15:56:02 -0400 [thread overview]
Message-ID: <20260422155602.26ef7c68@gandalf.local.home> (raw)
Linus,
ktest updates for v7.1:
- Fix month in date timestamp used to create failure directories
On failure, a directory is created to store the logs and config file to
analyze the failure. The Perl function localtime is used to create the
data timestamp of the directory. The month passed back from that
function starts at 0 and not 1, but the timestamp used does not account
for that. Thus for April 20, 2026, the timestamp of 20260320 is used,
instead of 20260420.
- Save the logfile to the failure directory
Just the test log is saved to the directory on failure, but there's
useful information in the full logfile that can be helpful to analyzing
the failure. Save the logfile as well.
Please pull the latest ktest-v7.1-2 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git
ktest-v7.1-2
Tag SHA1: 283ba465c80c5d6c3d6e9dce8cd621be8652a2d5
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(-)
---------------------------
diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl
index 112f9ca2444b..f94ed2e98887 100755
--- a/tools/testing/ktest/ktest.pl
+++ b/tools/testing/ktest/ktest.pl
@@ -1855,7 +1855,7 @@ sub save_logs {
my ($result, $basedir) = @_;
my @t = localtime;
my $date = sprintf "%04d%02d%02d%02d%02d%02d",
- 1900+$t[5],$t[4],$t[3],$t[2],$t[1],$t[0];
+ 1900+$t[5],$t[4]+1,$t[3],$t[2],$t[1],$t[0];
my $type = $build_type;
if ($type =~ /useconfig/) {
@@ -1878,6 +1878,12 @@ sub save_logs {
"testlog" => $testlog,
);
+ if (defined($opt{"LOG_FILE"})) {
+ if (-f $opt{"LOG_FILE"}) {
+ cp $opt{"LOG_FILE"}, "$dir/logfile";
+ }
+ }
+
while (my ($name, $source) = each(%files)) {
if (-f "$source") {
cp "$source", "$dir/$name" or
next reply other threads:[~2026-04-22 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 19:56 Steven Rostedt [this message]
2026-04-22 22:14 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2026-04-14 11:06 Steven Rostedt
2026-04-16 0:51 ` pr-tracker-bot
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=20260422155602.26ef7c68@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®