When running the ftrace selftests, 2 failures and 6 unresolved cases were observed. The failures can be avoided by setting a sysctl prior to test execution (fixed in patch 1) and the unresolved cases result from absence of testing modules which are built based on CONFIG options being set and program availability (fixed in patch 2).
These seem more like "unsupported" than "unresolved" errors, since for the ftrace tests "unresolved" cases cause the test (and thus kselftest) to report failure. With these changes in place, the unresolved cases become unsupported and the test failures disappear, resulting in the ftracetest program exiting with "ok" status.
Alan Maguire (2): ftrace/selftests: workaround cgroup RT scheduling issues ftrace/selftest: absence of modules/programs should trigger unsupported errors
tools/testing/selftests/ftrace/ftracetest | 23 ++++++++++++++++++++++ .../ftrace/test.d/direct/ftrace-direct.tc | 2 +- .../ftrace/test.d/direct/kprobe-direct.tc | 2 +- .../selftests/ftrace/test.d/event/trace_printk.tc | 2 +- .../ftrace/test.d/ftrace/func_mod_trace.tc | 2 +- .../ftrace/test.d/kprobe/kprobe_module.tc | 2 +- .../selftests/ftrace/test.d/selftest/bashisms.tc | 2 +- 7 files changed, 29 insertions(+), 6 deletions(-)