From: Theodore Ts'o <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Cc: mhalcrow@google.com
Subject: Re: Updated version of kvm-xfstests available
Date: Tue, 28 Oct 2014 11:20:30 -0400 [thread overview]
Message-ID: <20141028152030.GA9530@thunk.org> (raw)
In-Reply-To: <20140908020101.GD1066@thunk.org>
I've uploaded a new set of precompiled kvm-xfstests test appliances
at:
https://www.kernel.org/pub/linux/kernel/people/tytso/kvm-xfstests
This new version has an updated xfstests with some additional tests
enabled (some of which test bugs that were only fixed in the recent
merge window, so if you are testing older kernels, some of the new
tests may fail).
There aren't that many changes to the framework this time that are
visible to users. It is now possible to automatically build a local
mirror of the debian packages, and you can also update an existing
root_fs.img without regenerating the base OS image. Both of these
allow new root_fs images to be built more quickly and without
requiring network access, which is handy for people who are doing
xfstests development.
If you have a local git repository of xfstests-bld, make sure you do a
"git pull" to update the latest version of the kvm-xfstests shell
script. If you download the root_fs.img file from www.kernel.org, you
won't have build xfstests on your own. Just drop the root_fs.img file
in kvm-xfstests/test-appliance, look at kvm-xfstests/config and
override various parameters using ~/.config/kvm-xfstests or in the
kvm-xfstests/config.custom file. When you're ready, cd into the
kvm-xfstests directory, and then run "./kvm-xfstests smoke" and make
sure everything works.
Enjoy, and have fun!!
- Ted
P.S. There is a baseline run of ext4 for 3.18-rc2 available here:
ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/kvm-xfstests/baseline-3.18-rc2.xz
I'm seeing some oom-kills that affect generic/273 and generic/224 but
the tests do run to completion (which they weren't after 3.18-rc1 +
the ext4 commits for the merge window, or during the last development
cycle). It may be that the extent status tree shrinker patches will
address the remaining oom-kills.
prev parent reply other threads:[~2014-10-28 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 23:45 Updated versoin of kvm-xfstests available Theodore Ts'o
2014-08-12 16:08 ` Updated version " Theodore Ts'o
2014-08-12 16:10 ` Theodore Ts'o
2014-08-12 16:10 ` Theodore Ts'o
2014-08-23 17:35 ` Eric Whitney
2014-09-08 2:01 ` Theodore Ts'o
2014-10-28 15:20 ` 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=20141028152030.GA9530@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=mhalcrow@google.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;
as well as URLs for NNTP newsgroup(s).