On Mon, Jan 26, 2026 at 11:25:44AM +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 <[email protected]> > --- > tools/testing/selftests/ublk/test_common.sh | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/tools/testing/selftests/ublk/test_common.sh > b/tools/testing/selftests/ublk/test_common.sh > index ab1ea5cc904a..5865f1e640ce 100755 > --- a/tools/testing/selftests/ublk/test_common.sh > +++ b/tools/testing/selftests/ublk/test_common.sh > @@ -122,6 +122,7 @@ _prep_test() { > modprobe ublk_drv > /dev/null 2>&1 > UBLK_TMP=$(mktemp $TMPDIR/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() > @@ -166,6 +167,7 @@ _cleanup_test() { > "${UBLK_PROG}" del -a > > _remove_files > + echo "ublk selftest: $TID done at $(date --iso-8601=sec)" | tee > /dev/kmsg > }
Also `date "+%F %T"`(which is taken by blktests project) looks more readable, such as: [root@ktest-40 blktests]# date "+%F %T" 2026-01-26 14:00:51 [root@ktest-40 blktests]# date --iso-8601=sec 2026-01-26T14:01:54+00:00 So would you like to consider it too? Thanks, Ming
