All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Eryu Guan <guaneryu@gmail.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2 4/5] shared,generic: move shared/006 to generic/
Date: Fri, 5 Jul 2019 23:40:53 -0400	[thread overview]
Message-ID: <20190706034053.GB11665@mit.edu> (raw)
In-Reply-To: <20190705080757.GG7943@desktop>

On Fri, Jul 05, 2019 at 04:07:57PM +0800, Eryu Guan wrote:
> > +_require_scratch_inode_limits()
> > +{
> > +	_require_scratch
> > +	_scratch_mkfs > /dev/null 2>&1
> > +	_scratch_mount
> > +	if [ $(_get_free_inode $SCRATCH_MNT) -eq 0 ]; then
> > +		_notrun "$FSTYP does not have a fixed number of inodes available"
> > +	fi
> > +	_scratch_unmount
> > +}
> 
> I think testing against $TEST_DIR should be sufficient, so we could
> avoid the mkfs & mount & umount SCRATCH_DEV time.

I was following the pattern that I saw with other similar _require
tests (for example: _require_scratch_shutdown).  I *thought* the
reason why this is was done is because if the test only uses the
SCRATCH_DEV, there's no making it a requirement that TEST_DEV be
available --- since IIRC, we do support SCRATCH_DEV being available,
but not TEST_DEV.

I personally don't use xfstests in that way --- when I run xfstests,
TEST_DEV is always available and in some cases, SCRATCH_DEV won't be
present.  But I thought that's why _require_test exists --- so that
tests can be skipped if TEST_DEV does not exist.

      	     	     		      - Ted

  reply	other threads:[~2019-07-06  3:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 22:59 [PATCH v2 1/5] shared,ext4: move ext4-specific tests out of shared/ Theodore Ts'o
2019-06-28 22:59 ` [PATCH v2 2/5] check: add ext4 group list when testing ext2 and ext3 Theodore Ts'o
2019-06-28 22:59 ` [PATCH v2 3/5] shared,ext4: move ext[234]-specific tests out of shared/ Theodore Ts'o
2019-06-28 22:59 ` [PATCH v2 4/5] shared,generic: move shared/006 to generic/ Theodore Ts'o
2019-07-05  8:07   ` Eryu Guan
2019-07-06  3:40     ` Theodore Ts'o [this message]
2019-07-07 12:51       ` Eryu Guan
2019-06-28 22:59 ` [PATCH v2 5/5] shared,generic: move tests using duperemove " Theodore Ts'o

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=20190706034053.GB11665@mit.edu \
    --to=tytso@mit.edu \
    --cc=fstests@vger.kernel.org \
    --cc=guaneryu@gmail.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.