diff options
| author |   Masami Hiramatsu <mhiramat@kernel.org> | 2017-07-07 09:59:22 +0900 |
|---|---|---|
| committer |   Shuah Khan <shuahkh@osg.samsung.com> | 2017-07-26 15:41:13 -0600 |
| commit | 9b682cd4afeb239031c0646457de547001993066 (patch) | |
| tree | e1f794dcaf0e803467f1b3c1b183327ca5d5deaa /tools/testing/selftests/ftrace/ftracetest | |
| parent | selftests: breakpoint_test: Add missing line breaks (diff) | |
| download | wireguard-linux-9b682cd4afeb239031c0646457de547001993066.tar.xz wireguard-linux-9b682cd4afeb239031c0646457de547001993066.zip | |
selftests: ftrace: Do not failure if there is unsupported tests
Do not return failure exit code (1) for unsupported testcases,
since it is expected for stable kernels.
Previously, ftracetest is expected to run only on current
release for avoiding regressions. However, nowadays we run
it on stable kernels. This means some test cases must return
unsupported result. In such case, we should NOT exit
ftracetest with error status for unsupported results so that
kselftest (upper tests wrapper) shows it passed correctly.
Note that we continue to treat unresolved results as failure,
if test writers would like to notice user that the test result
should be reviewed, they can use exit_unresolved.
Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Acked-by: Steven Rostedt (VMware) <srostedt@goodmis.org>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
Diffstat (limited to 'tools/testing/selftests/ftrace/ftracetest')
| -rwxr-xr-x | tools/testing/selftests/ftrace/ftracetest | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/testing/selftests/ftrace/ftracetest b/tools/testing/selftests/ftrace/ftracetest index 14a03ea1e21d..290cd423df41 100755 --- a/tools/testing/selftests/ftrace/ftracetest +++ b/tools/testing/selftests/ftrace/ftracetest @@ -187,7 +187,7 @@ eval_result() { # sigval $UNSUPPORTED) prlog " [UNSUPPORTED]" UNSUPPORTED_CASES="$UNSUPPORTED_CASES $CASENO" - return 1 # this is not a bug, but the result should be reported. + return 0 # this is not a bug. ;; $XFAIL) prlog " [XFAIL]" |