On Oct 17, 2017, at 1:44 AM, Fathi Boudra fathi.boudra@linaro.org wrote:
On 17 October 2017 at 03:14, Tom Gall tom.gall@linaro.org wrote:
This past RC cycle I think we exposed a weakness in what we have in LKFT where the ability to execute some key functional stacks in the system to drive the kernel would probably be useful for validation.
The networking bug involving dhclient for example.
So what if we used either Debian, Gentoo or akin that has a mechanism that has as part of it’s packaging system a test target for each package. Simplest build a package, runs ‘make test’ (or akin) for some key packages that exercises parts of the system that should help tickle the kernel in interesting ways to tease out regressions.
OE has the same mechanism. It's called ptest.
Ok cool.
Thus wouldn’t work on modest boards but the socionext or Juno boards could probably work fine.
Thoughts?
I'm not convinced it would have helped in the above example.
I think that’s what we’d want to look into. Do some of the package test suites do enough to drive some representative activity in the kernel that could be useful for finding regressions.
I don’t think just universally do this for all 10,000+ packages for a distro or distro(s). Tho if we had a huge farm of servers we could shard out to …. anyway this seems like an interesting experiment that we could apply to 4.9.55-rc1 and see if it would have been detected.
Regards, Tom
Lts-dev mailing list Lts-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lts-dev