Re: [PATCH 1/3] MAINTAINERS: Introduce V: field for required tests

2023-11-22 Thread Theodore Ts'o
On Tue, Nov 21, 2023 at 01:27:44PM +, Mark Brown wrote: > > (I don't need to see all of the tests that passes; it's the test > > failures or the test flakes that are significant.) > > The listing of tests does get a bit more complex when you mix in running > on different platforms. Yeah,

Re: [PATCH 1/3] MAINTAINERS: Introduce V: field for required tests

2023-11-20 Thread Theodore Ts'o
On Mon, Nov 20, 2023 at 10:27:33PM +, Mark Brown wrote: > This is the sort of thing that kcidb (which Nikolai works on) is good at > ingesting, I actually do push all my CI's test results into there > already: > >https://github.com/kernelci/kcidb/ > > (the dashboard is down currently.)

Re: [PATCH 1/3] MAINTAINERS: Introduce V: field for required tests

2023-11-20 Thread Theodore Ts'o
On Mon, Nov 20, 2023 at 02:30:49PM +0100, Ricardo CaƱuelo wrote: > > This is not trivial because tests vary a lot and we'd first need to > define which artifacts to link to, and because whatever is linked (test > commands, output log, results summary) would need to be stored > forever. But since

Re: [PATCH 2/3] MAINTAINERS: Require kvm-xfstests smoke for ext4

2023-11-19 Thread Theodore Ts'o
On Fri, Nov 17, 2023 at 12:39:56PM +0530, Chandan Babu R wrote: > IMHO, For XFS, The value of "V" field should refer to xfstests rather than a > framework built around xfstests. This is because xfstests project contains the > actual tests and also we could have several frameworks (e.g. Kdevops)