On Wed, May 01, 2019 at 04:01:21PM -0700, Brendan Higgins wrote:
From: Felix Guo <felixguoxiuping(a)gmail.com>
The ultimate goal is to create minimal isolated test binaries; in the
meantime we are using UML to provide the infrastructure to run tests, so
define an abstract way to configure and run tests that allow us to
change the context in which tests are built without affecting the user.
This also makes pretty and dynamic error reporting, and a lot of other
nice features easier.
- parse .config and Kconfig files.
kunit_kernel.py: provides helper functions to:
- configure the kernel using kunitconfig.
- build the kernel with the appropriate configuration.
- provide function to invoke the kernel and stream the output back.
Signed-off-by: Felix Guo <felixguoxiuping(a)gmail.com>
Signed-off-by: Brendan Higgins <brendanhiggins(a)google.com>
Ah, here's probably my answer to my previous logging format question,
right? What's the chance that these wrappers output stuff in a standard
format that test-framework-tools can already parse? :)