From: "Darrick J. Wong" <djwong@kernel.org>
To: cem@kernel.org
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] Log kernel version in check.log
Date: Wed, 22 May 2024 07:42:41 -0700 [thread overview]
Message-ID: <20240522144241.GA25508@frogsfrogsfrogs> (raw)
In-Reply-To: <20240522113408.392468-1-cem@kernel.org>
On Wed, May 22, 2024 at 01:33:38PM +0200, cem@kernel.org wrote:
> From: Carlos Maiolino <cem@kernel.org>
>
> After collecting several xfstests runs, it's useful to keep track on
> which kernel a specific run happened.
>
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
I wonder if you want to capture more of the system variables, like
__generate_report_vars does?
(Should we be capturing ${FSTYP}progs version too?)
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> check | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/check b/check
> index c6dba89b..7703c128 100755
> --- a/check
> +++ b/check
> @@ -478,6 +478,7 @@ _wrapup()
> fi
>
> _global_log ""
> + _global_log "Kernel version: $(uname -r)"
> _global_log "$(date)"
>
> echo "SECTION -- $section" >>$tmp.summary
> --
> 2.45.1
>
>
next prev parent reply other threads:[~2024-05-22 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 11:33 [PATCH] Log kernel version in check.log cem
2024-05-22 14:42 ` Darrick J. Wong [this message]
2024-05-22 19:37 ` 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=20240522144241.GA25508@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=fstests@vger.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