| To: | Stefan Behrens <sbehrens@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] xfstests: before test execution, print test number to syslog |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Fri, 02 Mar 2012 09:29:14 -0600 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1330691215-4796-1-git-send-email-sbehrens@xxxxxxxxxxxxxxxx> |
| References: | <1330691215-4796-1-git-send-email-sbehrens@xxxxxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 |
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@xxxxxxxxxxxxxxxx> Reviewed-by: Eric Sandeen <sandeen@xxxxxxxxxx> 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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] xfstests: before test execution, print test number to syslog, Stefan Behrens |
|---|---|
| Next by Date: | Re: Poor performance using discard, Thomas Lynema |
| Previous by Thread: | Re: [PATCH] xfstests: before test execution, print test number to syslog, David Sterba |
| Next by Thread: | Re: [PATCH] xfstests: before test execution, print test number to syslog, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |