aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing
diff options
context:
space:
mode:
authorSteven Rostedt <srostedt@redhat.com>2010-11-08 16:49:25 -0500
committerSteven Rostedt <rostedt@goodmis.org>2010-11-18 11:23:11 -0500
commit7a849cd93ad2cf7d32427f3dbf5f524d5f588d20 (patch)
treeeb15ea56d4e26a21e01764c013df12a610ecab59 /tools/testing
parent21a9679feadf6b215c4f932b0df5d252b4822c45 (diff)
downloadkernel_samsung_espresso10-7a849cd93ad2cf7d32427f3dbf5f524d5f588d20.zip
kernel_samsung_espresso10-7a849cd93ad2cf7d32427f3dbf5f524d5f588d20.tar.gz
kernel_samsung_espresso10-7a849cd93ad2cf7d32427f3dbf5f524d5f588d20.tar.bz2
ktest: Output something easy to parse for failure or success
Have a easy way to parse the log file for success or failure. KTEST RESULT: ... Suggested-by: Tim Bird <tim.bird@am.sony.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'tools/testing')
-rwxr-xr-xtools/testing/ktest/ktest.pl4
1 files changed, 2 insertions, 2 deletions
diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl
index 962c0f7..e0e5935 100755
--- a/tools/testing/ktest/ktest.pl
+++ b/tools/testing/ktest/ktest.pl
@@ -378,7 +378,7 @@ sub fail {
doprint "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%\n";
doprint "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%\n";
- doprint "**** Failed: ", @_, " ****\n";
+ doprint "KTEST RESULT: TEST $i Failed: ", @_, "\n";
doprint "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%\n";
doprint "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%\n";
@@ -782,7 +782,7 @@ sub success {
doprint "\n\n*******************************************\n";
doprint "*******************************************\n";
- doprint "** TEST $i SUCCESS!!!! **\n";
+ doprint "KTEST RESULT: TEST $i SUCCESS!!!! **\n";
doprint "*******************************************\n";
doprint "*******************************************\n";