From: Eric Sandeen <sandeen@sandeen.net>
To: Alex Lyakas <alex@zadarastorage.com>, Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfstests updated to 197f773
Date: Wed, 29 Jan 2014 14:04:08 -0600 [thread overview]
Message-ID: <52E95EB8.8080003@sandeen.net> (raw)
In-Reply-To: <CAOcd+r1wUaMyrhvkq++WoswM1ND9+VZJNx0mZeC1Uiu663xbtg@mail.gmail.com>
On 1/29/14, 1:55 PM, Alex Lyakas wrote:
> Hi Dave,
> are all tests in xfstests (those relevant for XFS) in principle
> supposed to pass on XFS?
> I am running these tests on a pristine XFS from kernel 3.8.13
> (srcversion 9862FA08CF42E06A4151111) and I get:
>
> root@vc-13-12-1095-35-dev:/mnt/work/alex/xfstests# ./check tests/generic/013
> FSTYP -- xfs (non-debug)
> PLATFORM -- Linux/x86_64 vc-13-12-1095-35-dev 3.8.13-030813-generic
> MKFS_OPTIONS -- -f -bsize=4096 /dev/vdb
> MOUNT_OPTIONS -- /dev/vdb /mnt/SCRATCH_DIR
>
> generic/013 34s
> _check_xfs_filesystem: filesystem on /dev/vda is inconsistent (c) (see
> /mnt/work/alex/xfstests/results//generic/013.full)
uh, so it failed
> Ran: generic/013
> Passed all 1 tests
but it passed? ;)
The fact that you saw:
> generic/013 34s
and not:
> generic/013 34s ... 33s
or
> generic/013 34s ... output mismatch
or similar, makes me think the test did not even start, and /dev/vda was
corrupted before you even started the test, but I'm not certain.
/mnt/work/alex/xfstests/results//generic/013.full has more info.
Anyway, 013 generally passes AFAIK.
-Eric
> root@vc-13-12-1095-35-dev:/mnt/work/alex/xfstests# echo $?
> 1
>
> Thanks,
> Alex.
>
>
> On Fri, Jan 24, 2014 at 4:58 AM, Dave Chinner <david@fromorbit.com> wrote:
>> Hi all,
>>
>> The xfstests repository at git://oss.sgi.com/xfs/cmds/xfstests has
>> just been updated. Patches often get missed, so please check if your
>> outstanding patches were in this update. If they have not been in
>> this update, please resubmit them to xfs@oss.sgi.com so they can be
>> picked up in the next update.
>>
>> The new head of the master branch is commit:
>>
>> 197f773 xfstests: define $seqres in btrfs/026-029
>>
>> New Commits:
>>
>> Dave Chinner (7):
>> [ea0b6eb] xfs: test scratch device mkfs features
>> [b9b5d74] xfs: New _require_* tests for CRC enabled filesystems
>> [86e91cc] xfs: add fsstress/recovery test
>> [5b524ee] xfs/073, 208: remove .full output before starting the test
>> [b04b0fd] xfs: support xfs_metadump with external logs
>> [3ed573e] xfs/104: use fixed log size
>> [7657a10] generic/204: use fixed log size for XFS
>>
>> David Sterba (3):
>> [80622a6] xfstests: don't suggest to run full diff when DIFF_LENGTH is 0
>> [586a06c] xfstests: use value of FSTYP if defined externally
>> [1ed9046] xfstests: clean command names in btrfs tests
>>
>> Eric Sandeen (1):
>> [a93b1dd] ext4: regression test for ext4 resize with non-extent files
>>
>> Filipe David Borba Manana (1):
>> [8c427eb] xfstests: add test for btrfs incremental send infinite loop issue
>>
>> Koen De Wit (2):
>> [0c58766] xfstests: btrfs: cross-subvolume sparse copy
>> [197f773] xfstests: define $seqres in btrfs/026-029
>>
>>
>> Code Diffstat:
>>
>> README | 3 ++
>> check | 13 ++---
>> common/attr | 6 +++
>> common/rc | 122 +++++++++++++++++++++++++++---------------
>> tests/btrfs/003 | 2 +-
>> tests/btrfs/004 | 2 +-
>> tests/btrfs/007 | 4 +-
>> tests/btrfs/008 | 12 ++---
>> tests/btrfs/009 | 6 +--
>> tests/btrfs/013 | 2 +-
>> tests/btrfs/014 | 6 +--
>> tests/btrfs/015 | 2 +-
>> tests/btrfs/016 | 14 ++---
>> tests/btrfs/017 | 2 +-
>> tests/btrfs/019 | 14 ++---
>> tests/btrfs/022 | 6 +--
>> tests/btrfs/024 | 2 +-
>> tests/btrfs/025 | 4 +-
>> tests/btrfs/026 | 1 +
>> tests/btrfs/027 | 1 +
>> tests/btrfs/028 | 1 +
>> tests/btrfs/029 | 1 +
>> tests/btrfs/030 | 149 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>> tests/btrfs/030.out | 1 +
>> tests/btrfs/031 | 138 ++++++++++++++++++++++++++++++++++++++++++++++++
>> tests/btrfs/031.out | 48 +++++++++++++++++
>> tests/btrfs/group | 2 +
>> tests/ext4/306 | 82 +++++++++++++++++++++++++++++
>> tests/ext4/306.out | 13 +++++
>> tests/ext4/group | 1 +
>> tests/generic/204 | 4 ++
>> tests/generic/208 | 2 +
>> tests/shared/298 | 2 +-
>> tests/xfs/073 | 2 +
>> tests/xfs/104 | 2 +-
>> tests/xfs/186 | 1 +
>> tests/xfs/187 | 32 ++++++-----
>> tests/xfs/244 | 1 +
>> tests/xfs/253 | 3 +-
>> tests/xfs/278 | 1 +
>> tests/xfs/287 | 3 +-
>> tests/xfs/291 | 4 +-
>> tests/xfs/306 | 105 ++++++++++++++++++++++++++++++++++++
>> tests/xfs/306.out | 2 +
>> tests/xfs/group | 1 +
>> 45 files changed, 716 insertions(+), 109 deletions(-)
>>
>> --
>> Dave Chinner
>> david@fromorbit.com
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-01-29 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 2:58 [ANNOUNCE] xfstests updated to 197f773 Dave Chinner
2014-01-29 19:55 ` Alex Lyakas
2014-01-29 20:04 ` Eric Sandeen [this message]
2014-02-02 22:35 ` Dave Chinner
2014-02-04 17:53 ` Alex Lyakas
2014-02-04 22:23 ` 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=52E95EB8.8080003@sandeen.net \
--to=sandeen@sandeen.net \
--cc=alex@zadarastorage.com \
--cc=david@fromorbit.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;
as well as URLs for NNTP newsgroup(s).