From: Theodore Ts'o <tytso@mit.edu>
To: Steve French <smfrench@gmail.com>
Cc: fstests@vger.kernel.org
Subject: Re: xfstests and ext4
Date: Wed, 19 Nov 2014 15:02:52 -0500 [thread overview]
Message-ID: <20141119200252.GA15071@thunk.org> (raw)
In-Reply-To: <CAH2r5mti8hVXqmKu9kJg4Xk=5nkESCAQys1BFXhR6JSDVHOTEA@mail.gmail.com>
On Mon, Nov 17, 2014 at 08:35:39PM -0600, Steve French wrote:
>
> Yes. WIll do. It is a pain in test VMs to setup git with gmail two
> phase authentication
> but doable if I set it up to send mail from a different host.
There are lots of ways to skin a cat, but I just simply build xfstests
in my standard development environment, and then either create a
completely new test VM image from scratch, which doesn't take _that_ long:
<tytso@closure> {/u1/xfstests-bld/build-32/kvm-xfstests/test-appliance}
521% /usr/bin/time schroot -c sid -u root ./gen-image
...
/tmp/root_fs.raw.7430: 9867/65536 files (0.0% non-contiguous), 66071/262144 blocks
65.23user 15.65system 1:25.65elapsed 94%CPU (0avgtext+0avgdata 11076maxresident)k
42inputs+970048outputs (0major+1528344minor)pagefaults 0swaps
or I'll update the VM image from my build directory, which keeps the
OS files the same and only updates the files in /root/xfstests:
<tytso@closure> {/u1/xfstests-bld/build-32/kvm-xfstests/test-appliance}
523% /usr/bin/time schroot -c sid -u root -- ./gen-image --update
...
9.98user 1.65system 0:12.81elapsed 90%CPU (0avgtext+0avgdata 11644maxresident)k
4674inputs+178512outputs (0major+204070minor)pagefaults 0swaps
The advantage of doing it that way is that I get replicable builds for
my xfstest VM's, and it also helps keep them small (only 66 megs),
which makes them easier to move around to different test servers.
(I also like not being dependent on the version of xfslibs-dev that
Ubuntu might have decided to ship, since a while back I was stuck on
pretty ancient LTS versions due to corporate policy reasons, and there
were a few tests that required the latest versions of xfsprogs/xfslibs
in order to build and run. So that's why I use a completely hermetic
build in my infrastructure, which can be found in my xfstests-bld git
tree if you want to give it a try.)
Cheers,
- Ted
prev parent reply other threads:[~2014-11-19 20:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 23:38 xfstests and ext4 Steve French
2014-11-14 0:02 ` Dave Chinner
2014-11-14 1:20 ` Steve French
2014-11-17 20:38 ` Dave Chinner
2014-11-18 2:35 ` Steve French
2014-11-18 20:28 ` Dave Chinner
2014-11-19 19:07 ` Christoph Hellwig
2014-11-19 20:02 ` 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=20141119200252.GA15071@thunk.org \
--to=tytso@mit.edu \
--cc=fstests@vger.kernel.org \
--cc=smfrench@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.