Re: [RFC PATCH 5/6] selftests: run tests on nommu architecture
Hajime Tazaki <[email protected]>
| Newsgroups | org.kvack.linux-mm,org.infradead.lists.linux-um,org.kernel.vger.linux-kselftest |
|---|---|
| Message-ID | <[email protected]> |
Hello Mark, thank you for your time to review the patch ! On Fri, 14 Aug 2026 23:34:15 +0900, Mark Brown wrote: > > [1 <text/plain; us-ascii (quoted-printable)>] > On Fri, Aug 14, 2026 at 01:50:50PM +0100, Lorenzo Stoakes (ARM) wrote: > > > So at this point you're not really running much of the selftests at all, > > and are only happening to run those that don't do the very basic stuff > > nommu can't deal with. > > > I think an audit of existing tests to figure out what works with nommu vs > > what doesn't is really unreasonable again, given nobody tests or seemingly > > uses these arches. > > > So this patch might beget more nommu carve outs and exceptions and > > therefore nommu workload and maintenance, which isn't really sustainable. > > > I know I complain about lack of testing on nommu, but at the same time I > > don't think running arbitrary tests that happen to work on it and who knows > > if they are valid asserts anyway really fixes things. > > > And given nobody really is doing testing, it's not really a great RoI > > here... > > Perhaps a good first step here is to start off with getting some public > CI set up, then build up to getting things running cleanly. That way > there'll be visible ongoing coverage which will help motivate getting > whatever changes integrated, and if the changes are done bit by bit > there should be clearer explanations for why they make sense on nommu. thanks, I'm currently running tests on my personal CI (gh actions) but try to find a public one to be more visible to others. > You could perhaps use a skiplist to ignore tests that don't work yet so > the CI starts off clean? thanks, that would indeed make nommu tests more cleaner to integrate as a first step. -- Hajime