On Thu, Jun 23, 2022 at 08:31:30AM +0300, Amir Goldstein wrote: > To put it in more blunt terms, the core test suite, fstests, is not > very reliable. Neither kdevops nor fstests-bld address all the > reliability issue (and they contribute some of their own). > So we need the community to run both to get better and more > reliable filesystem test coverage. The generic pains with fstests / blktests surely can be shared and perhaps that is just a think we need to start doing more regularly at LSFMM more so than a one-off thing. > Nevertheless, we should continue to share as much experience > and data points as we can during this co-opetition stage in order to > improve both systems. Yes, my point was not about killing something off, it was about sharing data points, and I think we should at least share configs. I personally see value in sharing expunges, but indeed if we do we'd have to decide if to put them up on github with just the expunge list alone, or do we also want to upload artifacts on the same tree. Or should we dump all the artifacts into a storage pool somewhere. Some artifacts can grow to insane sizes if a test is bogus, I ran into one once which was at least 2 GiB of output on a *.bad file. The error was just reapeating over and over. I think IIRC it was for ZNS for btrfs or for a blktests zbd test where the ouput was just an error repeating itself over and over. We could just have a size limit on these. And if experience is to show us anyting perahps adopt an epoch thing if we use git. Luis
