summaryrefslogtreecommitdiffstats
path: root/lib/test_ubsan.c
diff options
context:
space:
mode:
authorDaniel Latypov <dlatypov@google.com>2022-11-21 11:55:26 -0800
committerShuah Khan <skhan@linuxfoundation.org>2022-12-12 14:13:47 -0700
commit309e22effb741a8c65131a2694a49839fd685a27 (patch)
tree96358f9ca4d5b02c7c8f76aeb774171fd6a7501c /lib/test_ubsan.c
parent0a7d5c30b7f02887319a1382fbb8dc1c8250fe2c (diff)
downloadlinux-309e22effb741a8c65131a2694a49839fd685a27.tar.bz2
kunit: tool: make --json do nothing if --raw_ouput is set
When --raw_output is set (to any value), we don't actually parse the test results. So asking to print the test results as json doesn't make sense. We internally create a fake test with one passing subtest, so --json would actually print out something misleading. This patch: * Rewords the flag descriptions so hopefully this is more obvious. * Also updates --raw_output's description to note the default behavior is to print out only "KUnit" results (actually any KTAP results) * also renames and refactors some related logic for clarity (e.g. test_result => test, it's a kunit_parser.Test object). Notably, this patch does not make it an error to specify --json and --raw_output together. This is an edge case, but I know of at least one wrapper around kunit.py that always sets --json. You'd never be able to use --raw_output with that wrapper. Signed-off-by: Daniel Latypov <dlatypov@google.com> Reviewed-by: David Gow <davidgow@google.com> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'lib/test_ubsan.c')
0 files changed, 0 insertions, 0 deletions