public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: alexander.tsvetkov@oracle.com
To: xfs@oss.sgi.com
Subject: XFStest suite problem
Date: Thu, 30 May 2013 12:07:14 +0400	[thread overview]
Message-ID: <51A708B2.2080701@oracle.com> (raw)

Hello,

There is a problem found in XFS tests suite: attempt to run XFS tests 
with some tests excluded from run, for example, "./check -g auto -X 231" 
causes the unexpected exclusion of some other tests (for example 
generic/127 in this case). Looking into suite's created exclude list 
indicates that it was incorrectly built by including some garbage 
together with correct test numbers records, so /tmp/30535.xlist looks like:

"generic/#!
generic//bin/bash
generic/#
generic/FSQA
generic/Test
generic/No.
generic/231
generic/#
generic/#
generic/Run
generic/fsx
generic/with
generic/quotas
generic/enabled
generic/and
generic/verify
generic/accounted
generic/quotas
generic/in
generic/the
generic/end
generic/#
generic/#
generic/Derived
generic/from
generic/test
generic/127
generic/#-----------------------------------------------------------------------
generic/#
generic/Copyright
generic/(c)
generic/2006
generic/Silicon
generic/Graphics,
..."

I think the following code of "check" script incorrectly builds this 
exclude list:

"-X) xfile=$2; shift ;
for d in $SRC_GROUPS $FSTYP; do
[ -f $SRC_DIR/$d/$xfile ] || continue
for f in `cat $SRC_DIR/$d/$xfile`; do
echo $d/$f >> $tmp.xlist
done
done
;;"

Used XFStests suite version from 2013-05-22.

Thanks,
Alexander Tsvetkov

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2013-05-30  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30  8:07 alexander.tsvetkov [this message]
2013-05-30 13:42 ` XFStest suite problem Eric Sandeen
2013-05-30 22:43   ` Dave Chinner

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=51A708B2.2080701@oracle.com \
    --to=alexander.tsvetkov@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox