| Message ID | 20190405205113.22762-3-seth.forshee@canonical.com |
|---|---|
| State | New |
| Headers | show |
| Series | fix selftests which fail due to missing modules | expand |
diff --git a/tools/testing/selftests/ftrace/ftracetest b/tools/testing/selftests/ftrace/ftracetest index 75244db70331..c55605d303fe 100755 --- a/tools/testing/selftests/ftrace/ftracetest +++ b/tools/testing/selftests/ftrace/ftracetest @@ -229,7 +229,7 @@ eval_result() { # sigval $UNRESOLVED) prlog " [${color_blue}UNRESOLVED${color_reset}]" UNRESOLVED_CASES="$UNRESOLVED_CASES $CASENO" - return 1 # this is a kind of bug.. something happened. + return 0 # this is a kind of bug.. something happened. ;; $UNTESTED) prlog " [${color_blue}UNTESTED${color_reset}]"
BugLink: https://bugs.launchpad.net/bugs/1823407 The ftrace selftests return an unresolved status when there was a problem with the test itself. In the aws kernel this happens for a couple of tests which use the trace_printk module, which is not shipped. Treat this like a skipped test rather than a failure. Signed-off-by: Seth Forshee <seth.forshee@canonical.com> --- tools/testing/selftests/ftrace/ftracetest | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)