selftests: cpufreq: Write test output to stdout as well
Subsystems (2)
PATCH 1/1 selftests: cpufreq: Write test output to stdout as well
Use 'tee' to send the test output to stdout in addition to the current output file. This makes the output easier to handle in automated test systems and is superior to only later dumping the output file contents to stdout, since this way the test output can be interleaved with other log messages, like from the kernel, so that chronology is preserved, making it easier to detect issues.
--- tools/testing/selftests/cpufreq/main.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/cpufreq/main.sh +1 -1
@@ -194,5 +194,5 @@ prerequisite # Run requested functions clear_dumps $OUTFILE -do_test >> $OUTFILE.txt +do_test | tee -a $OUTFILE.txt dmesg_dumps $OUTFILE
Signature · 1 line
2.34.1
Quoted 17 lines · Nícolas F. R. A. Prado
Use 'tee' to send the test output to stdout in addition to the current output file. This makes the output easier to handle in automated test systems and is superior to only later dumping the output file contents to stdout, since this way the test output can be interleaved with other log messages, like from the kernel, so that chronology is preserved, making it easier to detect issues.
Signed-off-by Nícolas F. R. A. Prado <[email protected]>--- tools/testing/selftests/cpufreq/main.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)tools/testing/selftests/cpufreq/main.sh +0
-0
tools/testing/selftests/cpufreq/main.sh prerequisite · line 198
Quoted 6 lines
tools/testing/selftests/cpufreq/main.sh +1
-1@@ -194,5 +194,5 @@ prerequisite # Run requested functions clear_dumps $OUTFILE -do_test >> $OUTFILE.txt +do_test | tee -a $OUTFILE.txt dmesg_dumps $OUTFILE
Signature · 1 line
viresh
Shuah Khan
maintainerQuoted 19 lines · Viresh Kumar
Quoted 18 lines · Nícolas F. R. A. Prado
Use 'tee' to send the test output to stdout in addition to the current output file. This makes the output easier to handle in automated test systems and is superior to only later dumping the output file contents to stdout, since this way the test output can be interleaved with other log messages, like from the kernel, so that chronology is preserved, making it easier to detect issues.
Signed-off-by Nícolas F. R. A. Prado <[email protected]>--- tools/testing/selftests/cpufreq/main.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)tools/testing/selftests/cpufreq/main.sh +0
-0@@ -194,5 +194,5 @@ prerequisite
Quoted 8 lines
tools/testing/selftests/cpufreq/main.sh prerequisite · line 198
Quoted 5 lines
tools/testing/selftests/cpufreq/main.sh +1
-1# Run requested functions clear_dumps $OUTFILE -do_test >> $OUTFILE.txt +do_test | tee -a $OUTFILE.txt dmesg_dumps $OUTFILEAcked-by Viresh Kumar <[email protected]>
Thank you. Applied to linux-kselftest fixes for rc2/3
thanks,
-- Shuah