ftrace/selftest: make unresolved cases cause failure if --fail-unresolved set
authorAlan Maguire <alan.maguire@oracle.com>
Wed, 19 Feb 2020 09:33:30 +0000 (09:33 +0000)
committerShuah Khan <skhan@linuxfoundation.org>
Fri, 1 May 2020 15:26:51 +0000 (09:26 -0600)
commitb730d668138cb3dd9ce78f8003986d1adae5523a
tree94d0695354319c60b4f6f23327e2a28621a8a543
parent57c4cfd4a2eef8f94052bd7c0fce0981f74fb213
ftrace/selftest: make unresolved cases cause failure if --fail-unresolved set

Currently, ftracetest will return 1 (failure) if any unresolved cases
are encountered.  The unresolved status results from modules and
programs not being available, and as such does not indicate any
issues with ftrace itself.  As such, change the behaviour of
ftracetest in line with unsupported cases; if unsupported cases
happen, ftracetest still returns 0 unless --fail-unsupported.  Here
--fail-unresolved is added and the default is to return 0 if
unresolved results occur.

Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
tools/testing/selftests/ftrace/ftracetest