On Wed, Jan 13, 2016 at 11:55:07AM -0500, Theodore Ts'o wrote: > On Wed, Jan 13, 2016 at 07:35:54AM +1100, Dave Chinner wrote: > > On Tue, Jan 12, 2016 at 02:52:48PM -0500, Eric Whitney wrote: > > > Duplicate the contents of the data_journal exclude file for the > > > data_journal_noleak test case. This will prevent failure reports from > > > tests already known to exercise unsupported online defrag functionality. > > > Add an explanatory comment to both exclude files for future reference. > > > > > > Signed-off-by: Eric Whitney <enwlinux@xxxxxxxxx> > > > > Can you please make these changes directly to xfstests rather than > > keeping information about what tests run under what circumstances in > > some external test wrapper? i.e. this can be implementing by adding > > a _requires_no_data_journal() check and adding it to each test. > > We've got a number of these exclusions, and some of them require > making changes that have been rejected by you previously as adding too > much hair that is ext4 specific. (For example, ways of restricting > the tests from using punch hole or collapse range.) > > So I'm carrying a number of these patches out of tree since they've > been rejected by upstream, and they are all necessary to make it to > exclude certain tests based on the ext4 configuration. I had assumed > you were philosophically against these sorts of exclusions except by > creating large numbers of extra xfstests groups, No, like all patches that people propose for inclusion, I look at them on a case by case basis and either take them or suggest better/different ways to implement the desired functionality. I'm always prepared to change my mind given sufficient justification/evidence of the benefit of a change. For stuff like test exclusions and config dependent test execution, the behaviour of xfstests has always been in flux. The general rule of thumb we've settled on recently is that if support/exclusion can be cleanly implemented as a _requires rule, then that's the way it should be done... > What would actually be cool is some way of expressing in a config file > tests that should be excluded given a certain file system > configuration and kernel version ranges, which would also serve as > documentation for when certain bugs were fixed/backported to the > stable kernels. We already have expunge files for this. xfstests not in the business of documenting what bug fixes are in what kernel - it's just a test harness and a bunch of tests. Fine grained execution environment constraints are the responsibility of the user, not the test harness. i.e. The xfstests harness can do coarse-grained "feature present" checks (i.e. _requires rules), but information about known bugs in certain envrionments needs to be provided to xfstests by the buggy environment... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- 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
