On Wed, Feb 10, 2016 at 10:34:55AM -0500, Theodore Ts'o wrote: > On Wed, Feb 10, 2016 at 04:45:31PM +1100, Dave Chinner wrote: > > On Tue, Feb 09, 2016 at 08:49:50PM -0500, Theodore Ts'o wrote: > > > There are no tmpfs specific tests, so tests/tmpfs does not exist. > > > Avoid print an error message caused by trying to read the file > > > tests/tmpfs/group (for example). > > > > > > Signed-off-by: Theodore Ts'o <tytso@xxxxxxx> > > > > Where does this error message get emitted? I would have expected > > lots of people to notice this (e.g. NFS, CIFS, ext2, ext3, gfs2) > > if this was causing some kind of problem long before this... > > It doesn't really cause a problem; it's more of a cosmetic issue, in > that it prints a harmless/annoying error message during the test > startup. It shows up if you specify a group, e.g. "check -g quick": > > BEGIN TEST tmpfs: tmpfs Wed Feb 10 10:31:09 EST 2016 > DEVICE: test:/tmp > MK2FS OPTIONS: > MOUNT OPTIONS: -o block_validity > ./check: line 96: tests/tmpfs/group: No such file or directory > FSTYP -- tmpfs > PLATFORM -- Linux/i686 kvm-xfstests 4.5.0-rc2ext4-00002-g6df2762 > MKFS_OPTIONS -- test:/scratch > MOUNT_OPTIONS -- -o size=1G test:/scratch /test/scratch > > generic/001 [10:31:10][ 5.811742] run fstests generic/001 Can you please rewrite the commit message to include this? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
