From: Ming Lei <ming.lei@redhat.com>
To: Alexander Atanasov <alex@zazolabs.com>
Cc: Shuah Khan <shuah@kernel.org>,
linux-block@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] selftests: ublk: mark each test start and end time in dmesg
Date: Tue, 27 Jan 2026 09:51:23 +0800 [thread overview]
Message-ID: <aXgaG606iOpF1ODS@fedora> (raw)
In-Reply-To: <20260126143158.1830011-1-alex@zazolabs.com>
On Mon, Jan 26, 2026 at 02:31:57PM +0000, Alexander Atanasov wrote:
> Log test start and end time in dmesg, so generated log messages
> during the test run can be linked to specific test from the test
> suite.
>
> Signed-off-by: Alexander Atanasov <alex@zazolabs.com>
> ---
> tools/testing/selftests/ublk/test_common.sh | 2 ++
> 1 file changed, 2 insertions(+)
>
> v1->v2:
> - rebase to latest block tree
> - include base-commit
>
> diff --git a/tools/testing/selftests/ublk/test_common.sh b/tools/testing/selftests/ublk/test_common.sh
> index 7ff6ce79d62c..e554e89e6e67 100755
> --- a/tools/testing/selftests/ublk/test_common.sh
> +++ b/tools/testing/selftests/ublk/test_common.sh
> @@ -121,6 +121,7 @@ _prep_test() {
> modprobe ublk_drv > /dev/null 2>&1
> UBLK_TMP=$(mktemp ublk_test_XXXXX)
> [ "$UBLK_TEST_QUIET" -eq 0 ] && echo "ublk $type: $*"
> + echo "ublk selftest: $TID starting at $(date --iso-8601=sec)" | tee /dev/kmsg
> }
>
> _remove_test_files()
> @@ -165,6 +166,7 @@ _cleanup_test() {
> "${UBLK_PROG}" del -a
>
> _remove_files
> + echo "ublk selftest: $TID done at $(date --iso-8601=sec)" | tee /dev/kmsg
As we talked, it could be more readable to follow blktests's date format of
`date "+%F %T"`, please do it in V3.
Thanks,
Ming
prev parent reply other threads:[~2026-01-27 1:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 14:31 [PATCH v2] selftests: ublk: mark each test start and end time in dmesg Alexander Atanasov
2026-01-27 1:51 ` Ming Lei [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=aXgaG606iOpF1ODS@fedora \
--to=ming.lei@redhat.com \
--cc=alex@zazolabs.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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