From: Eric Sandeen <sandeen@sandeen.net>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: before test execution, print test number to syslog
Date: Fri, 02 Mar 2012 09:29:14 -0600 [thread overview]
Message-ID: <4F50E74A.3070008@sandeen.net> (raw)
In-Reply-To: <1330691215-4796-1-git-send-email-sbehrens@giantdisaster.de>
On 3/2/12 6:26 AM, Stefan Behrens wrote:
> When the xfstests are executed in a batch (like "check 001-299")
> and produce syslog output, it is helpful to know which test was
> causing the output. Therefore each time a test is started, a
> syslog message is generated that contains the number of the
> xfstest.
>
> Signed-off-by: Stefan Behrens <sbehrens@giantdisaster.de>
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
I'd like to be sure others are ok with this, but I think
it's a good idea, thanks.
-Eric
> ---
> check | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/check b/check
> index f792009..883edcc 100755
> --- a/check
> +++ b/check
> @@ -241,6 +241,7 @@ do
> start=`_wallclock`
> $timestamp && echo -n " ["`date "+%T"`"]"
> [ ! -x $seq ] && chmod u+x $seq # ensure we can run it
> + logger "run xfstest $seq"
> ./$seq >$tmp.rawout 2>&1
> sts=$?
> $timestamp && _timestamp
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-02 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 12:26 [PATCH] xfstests: before test execution, print test number to syslog Stefan Behrens
2012-03-02 14:57 ` Eric Sandeen
2012-03-02 15:27 ` Stefan Behrens
2012-03-05 0:31 ` David Sterba
2012-03-02 15:29 ` Eric Sandeen [this message]
2012-03-05 1:23 ` Dave Chinner
2012-03-05 17:32 ` Stefan Behrens
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=4F50E74A.3070008@sandeen.net \
--to=sandeen@sandeen.net \
--cc=sbehrens@giantdisaster.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox