On Tue, Aug 15, 2023 at 02:10:40PM -0400, Sasha Levin wrote:

> My thinking was that the community could define a set of requirements
> that we expect to be tested before we're willing to let code sneak in,
> something along the lines of:

> 1. Built with GCC v1, v2, v3 for platforms x86, arm64, ... using
> allmodconfig/allyesconfig/allnoconfig/...

> 2. Built with Clang v1, v2, v3 for platforms x86, arm64, ... using
> allmodconfig/allyesconfig/allnoconfig/...

> 3. Run through LTP released in the past month.

> 4. Custom community provided tests, etc...

...and these tests pass!  :P

I'd also add booting on some set of qemu platform/firmware combinations
and the higher quality kselftest suites.  Guenter's tests would be good
too.

> The consequence of letting something sneak through will then be on us,
> and will probably trigger the addition of a test to the list of tests
> above.

Right.  I think the core thing is at least smoke testing.