On Fri, Jul 25, 2014 at 11:22:02AM -0400, Nick Krause wrote: > I was being sloppy. I screwed up if you want my help still, please > let me known. Well, tell you what. Why don't you start by downloading the following git repository: git://git.kernel.org/pub/scm/fs/ext2/xfstests-bld.git And then start by trying to use kvm-xfstests. There are some tests which are known failures; some are false positives, some are just bugs that we haven't gotten around to fixing. (This is especially true for bigalloc, which has a number of failures that still need to be tracked down.) The main rule that we follow is that we don't want to see any regressions. So extending kvm-xfstests by writing a script which analyzes the output of the get-results scripts so that regressions can be automatically flagged would be a good and useful thing to add. Another thing that would be useful is a script which automates using kvm-xfstests to drive "git bisect". Typically what happens after we discover a regression is to try to check and see of the failure is easily replicable using a single xfstests, and then to start bisecting from the baseline run where the test was successful, to try to find the guilty bisect. Automating this would be very useful. This will hopefully get you started on the testing side of things, which is also a good way to start learning about how ext4 works. Cheers, - Ted -- 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
