From: "Theodore Ts'o" <tytso@mit.edu>
To: fstests@vger.kernel.org
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Zorro Lang <zlang@kernel.org>
Subject: [PATCH] generic/773: fix expected output "QA output created by 1226"
Date: Thu, 13 Nov 2025 20:02:38 -0500 [thread overview]
Message-ID: <20251114010238.2173413-1-tytso@mit.edu> (raw)
The test generic/773 was apparently submitted as generic/1226, but
when it was renamed to pack the test namespace, apparently the test
output wasn't adjusted to reflect the new test name, leading to the
test failing on sytems that have devices that support atomic writes.
Fixes: 1499d4ff2365 ("generic: Add atomic write test using fio crc ...")
Cc: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: Zorro Lang <zlang@kernel.org>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
---
tests/generic/773 | 2 +-
tests/generic/773.out | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/generic/773 b/tests/generic/773
index 7ad745546..0a30ac7f4 100755
--- a/tests/generic/773
+++ b/tests/generic/773
@@ -2,7 +2,7 @@
# SPDX-License-Identifier: GPL-2.0
# Copyright (c) 2025 IBM Corporation. All Rights Reserved.
#
-# FS QA Test 1226
+# FS QA Test 773
#
# Validate FS atomic write using fio crc check verifier.
#
diff --git a/tests/generic/773.out b/tests/generic/773.out
index 6dce0ea52..8626114df 100644
--- a/tests/generic/773.out
+++ b/tests/generic/773.out
@@ -1,2 +1,2 @@
-QA output created by 1226
+QA output created by 773
Silence is golden
--
2.51.0
next reply other threads:[~2025-11-14 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 1:02 Theodore Ts'o [this message]
2025-11-14 6:43 ` [PATCH] generic/773: fix expected output "QA output created by 1226" Ojaswin Mujoo
2025-11-14 16:15 ` Zorro Lang
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=20251114010238.2173413-1-tytso@mit.edu \
--to=tytso@mit.edu \
--cc=fstests@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=zlang@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