From: "Theodore Ts'o" <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Brad Figg <brad.figg@canonical.com>,
linux-ext4@vger.kernel.org, xfs-oss <xfs@oss.sgi.com>
Subject: Re: Ubuntu Ext4 regression testing
Date: Wed, 12 Sep 2012 22:24:42 -0400 [thread overview]
Message-ID: <20120913022442.GB27544@thunk.org> (raw)
In-Reply-To: <50514061.2050801@redhat.com>
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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-09-13 2:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50511241.2090603@canonical.com>
2012-09-12 23:01 ` Ubuntu Ext4 regression testing Eric Sandeen
2012-09-12 23:15 ` Brad Figg
2012-09-13 0:20 ` Eric Sandeen
2012-09-13 0:41 ` Brad Figg
2012-09-13 1:51 ` Eric Sandeen
2012-09-13 2:04 ` Brad Figg
2012-09-13 2:09 ` Eric Sandeen
2012-09-13 2:17 ` Brad Figg
2012-09-13 2:24 ` Theodore Ts'o [this message]
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=20120913022442.GB27544@thunk.org \
--to=tytso@mit.edu \
--cc=brad.figg@canonical.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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