On Tue, Apr 08, 2014 at 08:55:04PM +1000, Dave Chinner wrote: > > If you check the xfstests commit history, I think you'll find that > Namjae wrote the xfstests that triggered the failure you are > seeing. > > You're just testing more esoteric configurations than most people do > - same as I do for XFS. We can't expect every developer to test > their code on every possible configuration before they submit > it.... ;) "kvm-xfstests -g smoke" takes about 4-5 hours to run[1], and allows all of the ext4 developers to run a much wider set of configurations. The more work they can do, the more I scale. This is one of the reasons why I'm pushing the testing automation so heavily. :-) - Ted [1] It's even faster if you run kvm-xfstests on a sacrificial ssd, or if you have a big enough machine to run using a series of 5g ramdisks. "kvm-xfstests -g auto" takes about 14 hours to run with spinning platters, so it's much more of a commitment. -- 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
