kunit: kunit_tool: Correctly parse diagnostic messages
authorDavid Gow <davidgow@google.com>
Tue, 10 Nov 2020 07:29:36 +0000 (23:29 -0800)
committerShuah Khan <skhan@linuxfoundation.org>
Tue, 1 Dec 2020 22:31:04 +0000 (15:31 -0700)
commit0c7a7e1a8ff3fb6d01467b43c62760e6bf0afab3
treeb41e40f9c37660b8c95f31bf50d06c8c8deba532
parent1f0e943df68ab407f523d9f47d96a535686a2293
kunit: kunit_tool: Correctly parse diagnostic messages

Currently, kunit_tool expects all diagnostic lines in test results to
contain ": " somewhere, as both the subtest header and the crash report
do. Fix this to accept any line starting with (minus indent) "# " as
being a valid diagnostic line.

This matches what the TAP spec[1] and the draft KTAP spec[2] are
expecting.

[1]: http://testanything.org/tap-specification.html
[2]: https://lore.kernel.org/linux-kselftest/CY4PR13MB1175B804E31E502221BC8163FD830@CY4PR13MB1175.namprd13.prod.outlook.com/T/

Signed-off-by: David Gow <davidgow@google.com>
Acked-by: Marco Elver <elver@google.com>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
tools/testing/kunit/kunit_parser.py