From: Michael Ellerman Date: Fri, 23 Mar 2018 09:44:27 +0000 (+1100) Subject: selftests: Print the test we're running to /dev/kmsg X-Git-Tag: v4.19~1266^2~1 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=88893cf787d3062c631cc20b875068eb11756e03;p=platform%2Fkernel%2Flinux-rpi.git selftests: Print the test we're running to /dev/kmsg Some tests cause the kernel to print things to the kernel log buffer (ie. printk), in particular oops and warnings etc. However when running all the tests in succession it's not always obvious which test(s) caused the kernel to print something. We can narrow it down by printing which test directory we're running in to /dev/kmsg, if it's writable. Example output: [ 170.149149] kselftest: Running tests in powerpc [ 305.300132] kworker/dying (71) used greatest stack depth: 7776 bytes left [ 808.915456] kselftest: Running tests in pstore Signed-off-by: Michael Ellerman Signed-off-by: Shuah Khan --- diff --git a/tools/testing/selftests/Makefile b/tools/testing/selftests/Makefile index a41b4be..f4dfee6 100644 --- a/tools/testing/selftests/Makefile +++ b/tools/testing/selftests/Makefile @@ -138,6 +138,7 @@ ifdef INSTALL_PATH echo "echo ; echo TAP version 13" >> $(ALL_SCRIPT); \ echo "echo Running tests in $$TARGET" >> $(ALL_SCRIPT); \ echo "echo ========================================" >> $(ALL_SCRIPT); \ + echo "[ -w /dev/kmsg ] && echo \"kselftest: Running tests in $$TARGET\" >> /dev/kmsg" >> $(ALL_SCRIPT); \ echo "cd $$TARGET" >> $(ALL_SCRIPT); \ make -s --no-print-directory OUTPUT=$$BUILD_TARGET -C $$TARGET emit_tests >> $(ALL_SCRIPT); \ echo "cd \$$ROOT" >> $(ALL_SCRIPT); \