While most tests use /bin/sh, they are dependent on /bin/sh being a
bash shell. Convert all the tests to execute via /bin/bash as it is
much, much simpler than trying to debug and remove all the bashisms
throughout the test code.
Signed-off-by: Dave Chinner <david@fromorbit.com>
Reviewed-by: Eric Sandeen <sandeen@sandeen.net>
Fix tests which would be affected by a change to lazy-sb
by default.
All tests now explicitly -specify- -l lazy-sb=1 where appropriate,
so this can go in prior to a userspace change.
Unfortunately many of the logprint outputs must just be taken on faith.
Also, the irix flavors for e.g. 018.op.irix will need fixing up
if anyone cares.
This also needs the patch I just sent for xfs_db clearing attr2
in bad_features2 to complete w/o error.
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Update test 082 for new filtred output
Update test 081 for new filtred output
Update test 018 for new filtred output
xfstests: filter out logprint inode version (and format)
Merge of master-melb:xfs-cmds:30583a by kenmcd.
Further mkfs options are then appended by _mkfs_log at mkfs time with _scratch_mkfs_xfs.
Currently there are a few ways mkfs options are specified in XFSQA:
1) suite wide MKFS_OPTIONS are specified before tests are run
e.g.
vimes:/home/fsgqa/kali/xfsqa/xfstests # export MKFS_OPTIONS="-l size=100m"
2) test wide MKFS_OPTIONS are specified during a particular test
e.g. 119
export MKFS_OPTIONS="-l version=2,size=1200b,su=64k"
3) mkfs options are appended by a test at mkfs time
e.g. 083
_scratch_mkfs_xfs -dsize=$fsz,agcount=$ags >>$seq.full
(4) Another form of appending is just appending to MKFS_OPTIONS directly
e.g. 114:export MKFS_OPTIONS="$MKFS_OPTIONS -i parent=1"
115:export MKFS_OPTIONS="$MKFS_OPTIONS -i paths=1"
e.g. Methods (2) *and* (3) for specifiying mkfs options are used in these tests.
This causes problems, because the mkfs options fallback code assumes the
_mkfs_log _scratch_mkfs_xfs appended options are the only test specified options.
This change causes tests using _mkfs_log to only use option (2).
~
~
Merge of master-melb:xfs-cmds:29031a by kenmcd.
for buf items - it's not useful for checking it generally.
Merge of master-melb:xfs-cmds:26358a by kenmcd.
filter out in the logprint filter, the new flags field that I added
for buf items - it's not useful for checking it generally.
and somehow me not checking in my 018.noquota.op change in ages ago
and left in my workarea.
This change was done at the time of a change to common.log but somehow
didn't get checked in.