[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20141113233804.GD28780@thunk.org>
Date: Thu, 13 Nov 2014 18:38:04 -0500
From: Theodore Ts'o <tytso@....edu>
To: Steve French <smfrench@...il.com>
Cc: Eric Sandeen <sandeen@...hat.com>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: xfstest generic/018 and ext4 defrag
On Thu, Nov 13, 2014 at 05:04:55PM -0600, Steve French wrote:
> Only other xfstest I saw failing on ext4 on 3.18-rc3 was generic/315
> (Ubuntu 14.10).
>
> generic/315 [failed, exit status 1] - output mismatch (see
> /home/sfrench/xfstests/results//generic/315.out.bad)
> --- tests/generic/315.out 2014-11-13 11:20:05.405440282 -0800
> +++ /home/sfrench/xfstests/results//generic/315.out.bad 2014-11-13
> 13:34:57.346960909 -0800
> @@ -1,2 +1,6 @@
> QA output created by 315
> Slience is golden
> +ls: cannot access /mnt/test/testfile.315: No such file or directory
> +./tests/generic/315: line 69: [: : integer expression expected
> +File size is changed to ( Bytes)
> +(see /home/sfrench/xfstests/results//generic/315.full for details)
That test works just fine for me. The test is pretty simple; if the
file is not getting created, it sounds like problem with the fallocate
command. I'd suggest trying to run the commands in tests/generic/315
by hand, and seeing what's going wrong, but I'm pretty sure this is a
configuration issue in your test environment.
This is one of the reasons why I set up the xfstests-bld /
kvm-xfstests infrastructure, BTW; it handles most of these setup
issues for ext4 developers who otherwise might not end up using
xfstests for regression testing.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists