On Sat, Sep 16, 2023 at 12:23:54PM +0300, Amir Goldstein wrote: > AFAIK, we never bothered to create two different baselines from scratch in > two different envs (e.g. libvirt and GCE/OCI) and compare them. The experience so far has been that sparse files help find more issues than using real drives and it is why its a default. And even if you use a cloud solution you can use sparse files too. Only recently did I add support to use real NVMe drive support and so to create partitions. That should find less issues, however I did the work so to be able to test LBS devices. > But as it is, you already have my baseline from libvirt/kvm - > I don't think that it makes sense to add to 6.1.y expunge lists > failures due to test env change, unless you were able to prove that either: > 1. Those tests did not run in my env > 2. You env manages to expose a bug that my env did not expose > > I can help with #1 by committing results from a run in my env. > #2 is harder - you will need to analyse the failures in your env > and understand them. My guess so far is that the older expunges used an older version of fstests. Luis
