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. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
