[Top] [All Lists]

xfstests test xfs/030 failure

To: xfs@xxxxxxxxxxx
Subject: xfstests test xfs/030 failure
From: Jan Kara <jack@xxxxxxx>
Date: Wed, 1 Oct 2014 11:45:39 +0200
Delivered-to: xfs@xxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)

  I'm getting failure for text xfs/030 like:
xfs/030 9s ... - output mismatch (see 
    --- tests/xfs/030.out       2014-09-30 19:36:53.000000000 +0200
    +++ /var/lib/xfstests/results//xfs/030.out.bad      2014-09-30 
22:11:38.000000000 +0200
    @@ -39,8 +39,8 @@
             - traversal finished ...
             - moving disconnected inodes to lost+found ...
     Phase 7 - verify and correct link counts...
    -Note - stripe unit (0) and width (0) fields have been reset.
    -Please set with mount -o sunit=<value>,swidth=<value>
    +Note - stripe unit (0) and width (0) were copied from a backup superblock.
    +Please reset with mount -o sunit=<value>,swidth=<value> if necessary
    (Run 'diff -u tests/xfs/030.out /var/lib/xfstests/results//xfs/030.out.bad' 
 to see the entire diff)

  Now obviously this is because I run xfsprogs 3.2.1 but xfstests have
message from older version of xfsprogs. What is a standard solution for
this? If I just replace the messages, then people with older xfsprogs will
see failures. So some kind of a filter?

Jan Kara <jack@xxxxxxx>

<Prev in Thread] Current Thread [Next in Thread>