From: Eric Sandeen <sandeen@sandeen.net>
To: Eric Sandeen <sandeen@redhat.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: log running test to dmesg
Date: Thu, 17 Jul 2014 23:37:35 -0500 [thread overview]
Message-ID: <53C8A48F.5080000@sandeen.net> (raw)
In-Reply-To: <534EF81D.20205@redhat.com>
On 4/16/14, 4:37 PM, Eric Sandeen wrote:
> We already log the running test to system logs via "logger"
> but viro pointed out that we can use /dev/kmsg to insert it
> into dmesg as well. When looking at the serial console that
> could be pretty useful.
>
> Thanks to viro for the test -w suggestion too.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
can we get this one in? Dave asked for a generic helper, but
no test needs to print to kmsg, and nobody else uses LOGGER_PROG.
All we use either one for is logging the test run.
If somebody needs it for another purpose, it makes sense to add a
helper...
-Eric
> ---
>
> diff --git a/check b/check
> index 268417c..09b2320 100755
> --- a/check
> +++ b/check
> @@ -457,6 +457,7 @@ do
> $timestamp && echo -n " ["`date "+%T"`"]"
> [ ! -x $seq ] && chmod u+x $seq # ensure we can run it
> $LOGGER_PROG "run xfstest $seqnum"
> + test -w /dev/kmsg && echo "run xfstest $seqnum" > /dev/kmsg
> ./$seq >$tmp.rawout 2>&1
> sts=$?
> $timestamp && _timestamp
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-07-18 4:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 21:37 [PATCH] xfstests: log running test to dmesg Eric Sandeen
2014-04-16 23:40 ` Dave Chinner
2014-04-17 1:43 ` Eric Sandeen
2014-07-18 4:37 ` Eric Sandeen [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=53C8A48F.5080000@sandeen.net \
--to=sandeen@sandeen.net \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.