diff options
| author | Daniel Latypov <dlatypov@google.com> | 2022-03-30 00:42:48 +0300 |
|---|---|---|
| committer | Shuah Khan <skhan@linuxfoundation.org> | 2022-05-12 20:15:58 +0300 |
| commit | 9660209d9418f2295d31fea0d32e313e9b2c1200 (patch) | |
| tree | 57ad822494fae14bfe479cf9b0350bea6ed84d61 /tools/perf/scripts/python | |
| parent | 3f0a50f345f78183f6e9b39c2f45ca5dcaa511ca (diff) | |
| download | linux-9660209d9418f2295d31fea0d32e313e9b2c1200.tar.xz | |
kunit: tool: print clearer error message when there's no TAP output
Before:
$ ./tools/testing/kunit/kunit.py parse /dev/null
...
[ERROR] Test : invalid KTAP input!
After:
$ ./tools/testing/kunit/kunit.py parse /dev/null
...
[ERROR] Test <missing>: could not find any KTAP output!
This error message gets printed out when extract_tap_output() yielded no
lines. So while it could be because of malformed KTAP output from KUnit,
it could also be due to not having any KTAP output at all.
Try and make the error message here more clear.
Signed-off-by: Daniel Latypov <dlatypov@google.com>
Reviewed-by: David Gow <davidgow@google.com>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions