[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120913022442.GB27544@thunk.org>
Date: Wed, 12 Sep 2012 22:24:42 -0400
From: Theodore Ts'o <tytso@....edu>
To: Eric Sandeen <sandeen@...hat.com>
Cc: Brad Figg <brad.figg@...onical.com>, linux-ext4@...r.kernel.org,
xfs-oss <xfs@....sgi.com>
Subject: Re: Ubuntu Ext4 regression testing
On Wed, Sep 12, 2012 at 09:09:37PM -0500, Eric Sandeen wrote:
>
> Ah, I didn't know that autotest had a snapshot. I wonder if there's
> a way to tease that back out, and pull down xfstests from git daily.
>
> FWIW, it's a little confusing - we have 2 repos:
>
> git://oss.sgi.com/xfs/cmds/xfstests.git
> git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
This may be helpful; I have a xfstests build environment here:
git://git.kernel.org/pub/scm/fs/ext2/xfstests-bld.git
It will automatically pull down the xfstests and xfsprogs from
git.kernel.org, and builds xfstests in a hermetic environment (i.e.,
it doesn't depend on version of xfsprogs, libacl, libaio,
etc. installed on the build system). I set this up back when I was
doing most of my work using Ubuntu LTS 10.04, and the positively
ancient versions of libacl, libaio, xfsprogs-dev, etc., weren't
compatible with the bleeding edge of xfstests.
So I used this build environment so I wasn't dependent on the
vagrancies of whatever happened to be in Ubunutu LTS 10.04.
The makefiles in xfstests-bld will also generate a tar file containing
the necessary xfstests and xfsprogs binaries which I could then drop
into a debootstrap environment (I'm currently using a x86-32 Debian
unstable chroot) which I then use in my KVM image. So it allows me to
get and build the very latest version of xfstests from git.kernel.org
in a highly automated fashion.
Regards,
- 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