Thread (131 messages) 131 messages, 12 authors, 2019-05-23

Re: [PATCH v2 04/17] kunit: test: add kunit_stream a std::stream like logger

From: Frank Rowand <hidden>
Date: 2019-05-02 21:19:04
Also in: dri-devel, linux-doc, linux-fsdevel, linux-kbuild, linux-kselftest, linux-um, lkml, nvdimm

On 5/2/19 1:25 PM, Brendan Higgins wrote:
On Thu, May 2, 2019 at 4:00 AM Greg KH [off-list ref] wrote:
quoted
On Wed, May 01, 2019 at 04:01:13PM -0700, Brendan Higgins wrote:
quoted
A lot of the expectation and assertion infrastructure prints out fairly
complicated test failure messages, so add a C++ style log library for
for logging test results.
Ideally we would always use a standard logging format, like the
kselftest tests all are aiming to do.  That way the output can be easily
parsed by tools to see if the tests succeed/fail easily.

Any chance of having this logging framework enforcing that format as
well?
I agree with your comment on the later patch that we should handle
this at the wrapper script layer (KUnit tool).
This discussion is a little confusing, because it is spread across two
patches.

I do not agree that this should be handled in the wrapper script, as
noted in my reply to patch 12, so not repeating it here.

-Frank
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help